Bug#586133: Boot process pauses indefinitely waiting for keyboard activity
Jonathan Bob, Kushal: ping? Sorry for not responding earlier. I think this one is a wild goose chase at least in my case it was like that. Also, I don't have access to the system anymore exhibiting the problem. Most likely this seems to be a BIOS/Firmware bug. Thanks. Kushal Koolwal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586133: Boot process pauses indefinitely waiting for keyboard activity
Do you remember what make and model that machine had? I think (vaguely remember) it was an Intel Menlow Platform with Phoenix BIOS. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652948: Rich Text Editor (FCKeditor) disabled
Roland, I ran into the same problem when I upgraded to Firefox 9.0. However, commenting the line in wikibits.js fixes the sidebar issue but at the same time the Rich Text Editor (FCKEditor) also gets disabled automatically and there is now way to enable it. Can you please explain your Adblock workaround in detail? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587703: Please close the issue...
Jonathan, Thanks for checking. Actually we were able to resolve this issue at the BIOS/Firmware level. There was some resource allocation issue in the ACPI's PNP devices. But just wanted to make it clear that we started seeing this issue from 2.6.32 onwards and hence the BIOS fix was necessary if we wanted to use kernel 2.6.32 or later. You can close this issue for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587703: System hangs at boot with PCIE Mini WiFi card attached
Weird. Do you mean that you changed some setting in the BIOS to fix this, or that you applied a BIOS update? Is there somewhere we can read about the firmware update (e.g., a BIOS changelog) to see if there is anything Linux could or should be doing to avoid similar problems in the future? No, it was not a CMOS settings change that fixed it. The fix was inside the BIOS code. It was more like a BIOS bug than a Linux bug. You can follow the thread here: https://bugzilla.kernel.org/show_bug.cgi?id=26732 Although the above thread talks slightly about different issue but AFAICAR the fix is same for both the issues (one mentioned on this bug report and the one mentioned on the Kernel Bugzilla). It's been quite a while so I can't recollect all the details accurately. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633787: mantis: Cannot upload .ko files -- APPLICATION ERROR #504
Package: mantis Version: 1.2.4-1 Severity: normal When I try to upload a file with .ko extension, say for example, pata_rdc.ko, on an existing mantis issue, I get the following error message: *** APPLICATION ERROR #504 No file was uploaded. Please go back and Choose a file before pressing Upload. *** I have not modified any default settings related to file upload. Also, I can upload files with extension .zip, .txt, etc. without any problems, so doesn't seem like a permission issue. I turned on $g_show_detailed_errors=ON and I get the following output: https://picasaweb.google.com/lh/photo/pz25p4bAecveWdgj- uPyJEJ50yjyYV84vHr415LdNsM?feat=directlink -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mantis depends on: ii apache22.2.16-6+squeeze1 Apache HTTP Server metapackage ii apache2-mpm-prefork [h 2.2.16-6+squeeze1 Apache HTTP Server - traditional n ii apache2-utils 2.2.16-6+squeeze1 utility programs for webservers ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libapache2-mod-php55.3.3-7+squeeze3 server-side, HTML-embedded scripti ii libjs-prototype1.6.1-1 JavaScript Framework for dynamic w ii libjs-scriptaculous1.8.3-1 JavaScript library for dynamic web ii libnusoap-php 0.7.3-4 SOAP toolkit for PHP ii libphp-adodb 5.10-1The ADOdb database abstraction lay ii libphp-phpmailer 5.1-1 full featured email transfer class ii php5-cli 5.3.3-7+squeeze3 command-line interpreter for the p ii ucf3.0025+nmu1 Update Configuration File: preserv Versions of packages mantis recommends: ii mysql-client-5.1 [mysql 5.1.49-3 MySQL database client binaries ii php5-mysql 5.3.3-7+squeeze3 MySQL module for php5 Versions of packages mantis suggests: ii mysql-server5.1.49-3 MySQL database server (metapackage ii mysql-server-5.1 [mysql 5.1.49-3 MySQL database server binaries and ii php5-cli5.3.3-7+squeeze3 command-line interpreter for the p -- Configuration Files: /etc/mantis/apache.conf changed [not included] /etc/mantis/config_local.php changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633128: debian-installer: Squeeze Installer fails to detect RDC PATA controller
Package: debian-installer Severity: important Tags: d-i Debian Squeeze Net Install disc fails to detect my RDC PATA controller when it tries to detect the disks. I end up with the dialog No disk drive was dtected. If you know the name of the driver needed by your disk drive, you can select from the list. Unfortunately, even the list of the drivers does not have the driver (pata_rdc) for the controller. My system is a VortexDX based 486 system. The driver support for this IDE controller has been in the Linux kernel since 2.6.32. http://lxr.linux.no/#linux+v2.6.32/drivers/ata/pata_rdc.c Interestingly, if I attach a hard drive to my system with Debian Squeeze (2.6.32-5-486) already installed, the kernel boots just fine and loads the pata_rdc driver: debian:~# lsmod Module Size Used by acpi_cpufreq3622 0 processor 23003 1 acpi_cpufreq thermal_sys 9346 1 processor cpufreq_powersave602 0 cpufreq_userspace 1304 0 cpufreq_conservative 3902 0 cpufreq_stats 1592 0 fuse 43201 3 loop9573 0 psmouse48562 0 evdev 5520 3 pcspkr 1235 0 serio_raw 2912 0 ext3 92740 1 jbd27954 1 ext3 mbcache 3482 1 ext3 usbhid 27576 0 hid50948 1 usbhid sd_mod 25957 3 crc_t10dif 1012 1 sd_mod ata_generic 2059 0 ohci_hcd 17179 0 pata_rdc2789 2 libata117307 2 ata_generic,pata_rdc r6040 8056 0 ehci_hcd 28827 0 scsi_mod 102293 2 sd_mod,libata usbcore98489 4 usbhid,ohci_hcd,ehci_hcd mii 2654 1 r6040 nls_base4445 1 usbcore Here is the relevant output of lspci -vvxx for IDE controller: 00:0c.0 IDE interface: RDC Semiconductor, Inc. Device 1011 (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: RDC Semiconductor, Inc. Device 1011 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 16 bytes Interrupt: pin A routed to IRQ 14 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at ef00 [size=16] Kernel driver in use: pata_rdc 00: f3 17 11 10 05 00 00 02 01 8a 01 01 04 40 00 00 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 20: 01 ef 00 00 00 00 00 00 00 00 00 00 f3 17 11 10 30: 00 00 00 00 00 00 00 00 00 00 00 00 0e 01 00 00 It seems that the Debian Installer uses the exact same kernel (2.6.32-5-486), so why does it fails to detect my RDC PATA controller whereas it just works fine on an installed Debian Squeeze hard drive. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633128: Acknowledgement (debian-installer: Squeeze Installer fails to detect RDC PATA controller)
OK, I think I figured out why Debian Squeeze won't detect my pata controller... # dpkg -x /media/cdrom0/pool/main/l/linux-kernel-di-i386-2.6/pata-modules-2.6.32-5-486-di_1.99+squeeze3_i386.udeb /root/ # ls -l /root/lib/modules/2.6.32-5-486/kernel/drivers/ata/ total 260 -rw-r--r-- 1 root root 14468 Jun 13 03:00 pata_ali.ko -rw-r--r-- 1 root root 15600 Jun 13 03:00 pata_amd.ko -rw-r--r-- 1 root root 9164 Jun 13 03:00 pata_artop.ko -rw-r--r-- 1 root root 8344 Jun 13 03:00 pata_atiixp.ko -rw-r--r-- 1 root root 9656 Jun 13 03:00 pata_cmd64x.ko -rw-r--r-- 1 root root 10064 Jun 13 03:00 pata_cs5520.ko -rw-r--r-- 1 root root 9512 Jun 13 03:00 pata_cs5530.ko -rw-r--r-- 1 root root 7664 Jun 13 03:00 pata_efar.ko -rw-r--r-- 1 root root 16136 Jun 13 03:00 pata_it821x.ko -rw-r--r-- 1 root root 5668 Jun 13 03:00 pata_jmicron.ko -rw-r--r-- 1 root root 6824 Jun 13 03:00 pata_marvell.ko -rw-r--r-- 1 root root 7544 Jun 13 03:00 pata_mpiix.ko -rw-r--r-- 1 root root 5984 Jun 13 03:00 pata_netcell.ko -rw-r--r-- 1 root root 6984 Jun 13 03:00 pata_ns87410.ko -rw-r--r-- 1 root root 7220 Jun 13 03:00 pata_oldpiix.ko -rw-r--r-- 1 root root 12164 Jun 13 03:00 pata_pdc2027x.ko -rw-r--r-- 1 root root 8804 Jun 13 03:00 pata_pdc202xx_old.ko -rw-r--r-- 1 root root 6552 Jun 13 03:00 pata_rz1000.ko -rw-r--r-- 1 root root 6772 Jun 13 03:00 pata_sc1200.ko -rw-r--r-- 1 root root 6672 Jun 13 03:00 pata_sch.ko -rw-r--r-- 1 root root 10820 Jun 13 03:00 pata_serverworks.ko -rw-r--r-- 1 root root 10292 Jun 13 03:00 pata_sil680.ko -rw-r--r-- 1 root root 7368 Jun 13 03:00 pata_triflex.ko -rw-r--r-- 1 root root 14148 Jun 13 03:00 pata_via.ko root@debian:~# The RDC PATA controller driver, *pata_rdc*, is missing from the list. Can this be fixed in the next update (6.0.x.x) of Debian Squeeze? Thanks. Kushal Koolwal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575347: Request for help
Sils, I saw that some help was requested to test Mantis 1.2.X version on Debian. I would be happy to help with that. We have been using Mantis (on Debian Squeeze) for quite some time in our company. Also, I have been using Debian for over 4 years now and I am quite familiar with it. You can email me instructions on what kind of environment should I set up and how can I get started. Kushal Koolwal http://linux.koolsolutions.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615903: LXDE menu does not populate completely on booting from CD.
Package: bootcd Version: 3.23 Severity: normal Tags: patch It seems that since Debian Squeeze, LXDE depends on writing to ~/.cache directory to completely populate the LXDE menu. debian-squeeze:~# ls -al .cache/menus/ total 16 drwxr-xr-x 2 root root 4096 2011-02-25 15:39 . drwxr-xr-x 3 root root 4096 2011-02-11 14:23 .. -rw--- 1 root root 2705 2011-02-25 16:22 3df80abee392997597f2fcb4e42696df -rwxr-xr-x 1 root root 2396 2011-02-14 14:17 733773b31cfad39c82ddca9f6bff4758 The .cache directory was not present in Debian Lenny and hence this proplem did not occur on it. Solution is to exclude .cache directory in $NOT_TO_RAM variable in bootcdwrite.conf file. I am attaching the following patch to fix this: --- bootcd-3.23/bootcdwrite.conf2011-02-28 13:29:12.0 -0800 +++ bootcd-3.23-dev/bootcdwrite.conf2011-02-28 13:31:58.0 -0800 @@ -52,7 +52,7 @@ # exclude some files or directories from loading to ram # Because most people's home and root dir are to large to include # in RAM, subdirectories can be excluded: -NOT_TO_RAM=$(find $SRCDISK/home $SRCDISK/root -maxdepth 1 -mindepth 1 -type d) +NOT_TO_RAM=$(find $SRCDISK/home $SRCDISK/root -maxdepth 1 -mindepth 1 -type d | grep -v .cache) # If you are using ssh it is helpful to have a unique ssh hostkey for # each CD. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bootcd depends on: ii bootcd-i386 3.23 bootcd extension to create images ii cpio 2.11-4 GNU cpio -- a program to manage ar ii dosfstools3.0.9-1utilities for making and checking ii fdutils 5.5-20060227-4 Linux floppy utilities ii file 5.04-5 Determines file type using magic ii genisoimage 9:1.1.11-1 Creates ISO-9660 CD-ROM filesystem ii realpath 1.15 Return the canonicalized absolute Versions of packages bootcd recommends: ii wodim 9:1.1.11-1 command line CD/DVD writing tool Versions of packages bootcd suggests: ii bootcd-mkinitramfs3.23 initramfs extension for bootcd pn ssh none (no description available) -- no debconf information --- bootcd-3.23/bootcdwrite.conf2011-02-28 13:29:12.0 -0800 +++ bootcd-3.23-dev/bootcdwrite.conf2011-02-28 13:31:58.0 -0800 @@ -52,7 +52,7 @@ # exclude some files or directories from loading to ram # Because most people's home and root dir are to large to include # in RAM, subdirectories can be excluded: -NOT_TO_RAM=$(find $SRCDISK/home $SRCDISK/root -maxdepth 1 -mindepth 1 -type d) +NOT_TO_RAM=$(find $SRCDISK/home $SRCDISK/root -maxdepth 1 -mindepth 1 -type d | grep -v .cache) # If you are using ssh it is helpful to have a unique ssh hostkey for # each CD.
Bug#533565: Occurs on 2.6.37
I have verified that this issue still occurs on the latest stable kernel (2.6.37) from kernel.org and obviously on Debian Squeeze too. What would it take to report this bug upstream? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Nice!
I was about to write a long post on how to get the Poulsbo driver working (with 3D) on Debian Squeeze using the native sources (non EMGD) but I guess I will hold on to that (for now) since the kernel component is in the staging trees. I guess once those are stabilized in the kernel, we should be able to do a xserver-xorg-video-psb package for Debian which was the original intend for this bug report over 20 months ago -:) Thanks for posting the LKML link, Mattia! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533565: Kernel boot parameter fixes this problem
It seems that upon passing the kernel boot parameter libata.force=40c solves the problem. Should I still report this upstream? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586133: Same here with 2.6.32
I have found the same problem. The system waits for a keyboard input activity to boot further. Also I have found that it happens during shutdown also. Also this happens more when you disable Periodic SMI option in the BIOS. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
Bug#587703: linux-image-2.6-686: System hangs at boot with PCIE Mini WiFi card attached
card attached 2.6.32, 2.6.33 and 2.6.34 - Hangs at boot with Wifi card attached Since squeeze might ship with 2.6.32 kernel I thought I would get this bug report in before it is finalized. Please let me know if you want any other kind of logs or if you would like me to do some additional testing. Thanks Kushal Koolwal -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.32-5-686 2.6.32-15 Linux 2.6.32 for modern PCs linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523964: linux-image-2.6.28-1-486: memory corruption on resuming from STR/ACPI State 3
Hi Moritz, Sorry for not seeing your message earlier. Actually I have not been checking this email address any more but just happen to log in. Does this error still occur with the 2.6.30 kernel from unstable? I had to disable the following option in 2.6.28-1-486 in order to get rid of the error: # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set Let me know if you need more information. I have bookmarked the BUG report page so I will know if there is any new reply from you. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. http://clk.atdmt.com/GBL/go/196390706/direct/01/
Bug#533450: psb and iegd
My experience with iegd driver was exactly opposite with Debian Lenny. It won't compile in the first place. May be I was using an older version of iegd driver? However the psb sources from Ubuntu Jaunty always worked for me on Lenny, Squeeze and Unstable with 3D working on Squeeze and Unstable. A very disappointing scenario for Linux users. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/196390710/direct/01/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: maintaining poulsbo in Debian
Same. But as said in my previous mail, I've ommitted some patching you did.. will try that later, but not sure if I find the time today... If you are just installing from the pre-compiled packages you don't need modifications. Those packages should have everything that you need to get GMA working (I think). I would be interested to know about your results. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail: Trusted email with Microsoft's powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141664/direct/01/ http://clk.atdmt.com/GBL/go/177141664/direct/01/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: maintaining poulsbo in Debian
Holger, What kernel version are you using on Squeeze? The packages that I pointed you should work on 2.6.30 kernel on Squeeze. As Julien suggested first get the kernel component working. Try the following to get the kernel component working: # apt-get install linux-image-2.6-686 ; Just to make sure if you have the default kernel installed. and then install the following package: http://blogs.koolwal.net/wp-content/uploads/debian/packages/psb/xorg/psb-modules_4.41.1-1squeeze1_i386.deb # dpkg -i psb-modules_4.41.1-1squeeze1_i386.deb This will install modules in the default kernel: debian-tablet:/home/kushalk# ls /lib/modules/2.6.30-2-686/updates/char/drm/ drm.ko psb.ko and then do the following: # cd /lib/modules/2.6.30-2-686/updates/char/drm # cp psb.ko drm.ko ../../../kernel/drivers/gpu/ # rm -rf ../../../kernel/driver/gpu/drm/ # depmod -ae and then reboot and check your dmesg. The above worked for me on a 2.6.30-2-686 kernel. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurantsform=MFESRPpubl=WLHMTAGcrea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: maintaining poulsbo in Debian
Hi Holger, First of all many many thanks for taking the initiative on the PSB front. We all know that so far getting psb to work is a pain. but no real success so far.. As Adam asked, what problem are you facing? Are you able to build the psb and drm component? Couple of weeks back I wrote a step-by-step guide [1] to get psb working on Debian Squeeze. Please give a shot to these pre-built squeeze packages [2] and see if they work for you or not. I have been able to build the driver against Lenny, Squeeze and Testing. 3D did not work in Lenny because of lack of dri2 (I think) in the Lenny's XOrg version. Basically I took changes from Adam repo and added couple of more changes to get it working. For example, I had to remove the dpatch lines from debian/rules and added the relevant changes to file drm_sysfs.c directly. Also make sure that Option Ignore ACPI 1 line is un-commented in xorg.conf. Of course there are some ugly hacks as overwriting libdrm files and some odd symlinking to get them working as Adam mentioned. All these details are captured in [1]. I would be more than happy to extend any help that you may need in creating these packages for Debian. Thanks. [1] http://blogs.koolwal.net/2009/11/05/howto-compiling-intel-atom-poulsbo-gma-500-graphics-driver-on-debian/ [2] http://blogs.koolwal.net/wp-content/uploads/debian/packages/psb/xorg/ Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows 7: It works the way you want. Learn more. http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Step-by-step guide for Poulsbo module compilation
I know it is not pretty but it is thereSomething is better than nothing??? Here is a step-by-step guide: http://blogs.koolwal.net/2009/11/05/howto-compiling-intel-atom-poulsbo-gma-500-graphics-driver-on-debian/ Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurantsform=MFESRPpubl=WLHMTAGcrea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536537: What to fix in BIOS?
I too encountered the same problem on our Intel Atom (Poulsbo chipset) based computer running Debian 5.0. Upon looking at the file reboot.c in the kernel I found that the following two works for me: reboot=bios reboot=acpi Now at this point of time I am not sure if this is a BIOS issue or a kernel issue. How about a fixed bios?Bastian - I do have access to the person who writes the BIOS for this computer. I am not a BIOS expert by any chance but can you give me some idea/hint as to what should I be asking the BIOS guy to look into in order to fix this issue? Thank you. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Bing™ brings you maps, menus, and reviews organized in one place. Try it now. http://www.bing.com/search?q=restaurantsform=MLOGENpubl=WLHMTAGcrea=TXT_MLOGEN_Local_Local_Restaurants_1x1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Success on Lenny but 3D not working
So I was able to get the Poulsbo 3D driver working on Debian Lenny (using 2.6.30 kernel), That's a typo. Sorry about that. I meant I got Poulsbo 2D driver working on Lenny but not the 3D driver because of lack of dri2 module. Not sure what is this new dri2 stuff. If anybody knows how to generate dri2 modules in Lenny please let us know. So far I have been able to generate dri2 module only in Sid. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Success on Lenny but 3D not working
So I was able to get the Poulsbo 3D driver working on Debian Lenny (using 2.6.30 kernel), however 3D is not working because the xserver package in Lenny (and in Testing) does not have libdri2.so module and hence the *Load dri2* statement in the xorg.conf file fails. Not sure what is this new dri2 stuff. Also I am summarizing some of the hacks/overwrites that I had to do in order to get it working on Lenny. Most of them are same as from Adam's email in which he nicely points them out. Here they are anyways for Lenny: 1. Had to force-overwrite the libdrm.so.2 file while installing libdrm-poulsbo1 package 2. Had to force-overwrite the libexa.so file while installing xserver-xorg-video-psb package 3. Symlink /usr/lib/libdrm.so.2.3.0 to /lib/ 4. Comment the *Load dri2* line in the xorg.conf file in case if it is there. 5. You need to install the dkms package from testing in order to compile the psb-kernel-source package. Once the above steps are done, I can start my X server without any problems. I am not a Xorg expert or a DD by any chance, so I am not sure how to avoid the above steps. It would be nice if somebody can cleanly create these packages (without doing the hacks) and put them on Debian testing/sid. Thanks. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Some success
I have got X working now, but only by force-overwriting files in the libdrm2 package and deleting a libdrm.so.2.4*-file by hand, adding a symlink in /lib/ to the libdrm from the libdrm-poulsbo1 package. So I spend a good chunk of my weekend getting up Xorg driver running. I was able to compile the packages and install them on my Debian unstable (2.6.30-1-686) system after following Adam's instructions (thanks). Now upon rebooting, the psb framebuffer driver kicks in and then X server tries to start but fails with the following error messages: debian:~# cat /var/log/Xorg.0.log | grep (EE) (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) PSB(0): the stolenBase is:0x1f80 (EE) PSB(0): screnIndex is:0;fbPhys is:0x1f80; fbsize is:0x007df000 (EE) PSB(0): Could not find a valid initial configuration for this screen. (EE) Screen(s) found, but none have a usable configuration. debian:~# I am attaching my entire xorg.conf and Xorg.0.log file. Adam, do you mind posting your xorg.conf file? Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Bing™ finds low fares by predicting when to book. Try it now. http://www.bing.com/travel/deals/airline-ticket-deals.do?form=MTRHPGpubl=WLHMTAGcrea=TXT_MTRHPG_Travel_Travel_TravelDeals_1x1 Xorg.0.log Description: Unix manual page xorg.conf Description: Binary data
Bug#533450: Never Mind
I found what was causing the error. Actually it was buried inside the log file. All I had to do was to add the IgnoreACPI option in the Device section. Also note that once I installed all the packages I gave the command: X -configure cp /root/xorg.conf.new /etc/X11/xorg.conf and added the IgnoreACPI option in the xorg.conf file. Now I have Xorg running on Debian unstable with 3D working. Now only if I can figure out what additional changes needs to make it run on Debian stable. Thank you Adam for providing all the important information. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™ Photos: it's easy to store and manage your photos online. See how. http://windowslive.com/Online/Photos?ocid=TXT_TAGLM_WL_CS_PH_store_manage_072009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: Some success
Hi Adam, Last few days I have been trying to get the XOrg psb driver working on Lenny based on [1]. I had a partial success with it - I got the kernel drm stuff working (psb.ko and drm.ko) and I get a psb framebuffer console during the boot. However when my X server starts I get the following message: xf86MapVidMem: Could not mmap framebuffer (0×, 0xdfe8) (Cannot allocate memory) In case if you want to try the approach in [1], I can email you my steps. I think I am pretty close to get it working but I would still like to try your approach. You mentioned that you were able to get the packages compiled from PPA Jaunty source on your Debian unstable without pulling the entire Xorg from Ubuntu? Do you mind giving summary of your steps as to how you did it? I tried to build the xserver-xorg-video-psb package but I get packages dependency error as some of the packages that are require are not in unstable: *** checking for XORG... configure: error: Package requirements (xorg-server= 1.0.99.901 xproto fontsproto xf86dgaproto xineramaproto randrproto renderproto videoproto xf86miscproto xextproto) were not met: No package 'xf86dgaproto' found No package 'xineramaproto' found No package 'xf86miscproto' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XORG_CFLAGS and XORG_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. *** How did you get past this error? Did you end up downloading the missing packages from Ubuntu? Your help will be greatly appreciated. [1] http://www.happyassassin.net/2009/05/13/native-poulsbo-gma-500-graphics-driver-for-fedora-10/ Kushal Koolwal I do blog at http://blogs.koolwal.net/ From: kushalkool...@hotmail.com To: zerop...@gmail.com CC: 533...@bugs.debian.org Subject: RE: Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500) Date: Tue, 30 Jun 2009 09:46:00 -0700 Awesome! Thank you for your time and detailed steps, Most of the needed packages seem to be easy enough to get moves over to debian, but what we really seem to need is xserver-xorg-video-psb to be built against debian's xorg. Yes, it seems that if I try to install Xorg from Lenny it, it tries to remove the psb packages and vice versa. I don't know enough about Xorg system, but I am ready to spare some time to get the psb packages working in Debian. If there is some sort of similar example from the past on how to port packages from Ubuntu to Debian, I can give it a shot. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Lauren found her dream laptop. Find the PC that’s right for you. http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290 _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500)
Awesome! Thank you for your time and detailed steps, Most of the needed packages seem to be easy enough to get moves over to debian, but what we really seem to need is xserver-xorg-video-psb to be built against debian's xorg. Yes, it seems that if I try to install Xorg from Lenny it, it tries to remove the psb packages and vice versa. I don't know enough about Xorg system, but I am ready to spare some time to get the psb packages working in Debian. If there is some sort of similar example from the past on how to port packages from Ubuntu to Debian, I can give it a shot. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Lauren found her dream laptop. Find the PC that’s right for you. http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500)
Hi Scott, Thank you for the valuable information. I tried searching for the ppa archive for Intrepid but was not able to find the driver package. Do you have a link from where you found that driver? So if I understand you correctly, you installed a base Debian Lenny system. And then you added the intrepid packages repo to your sources.list file and installed XOrg from intrepid? For example: # apt-get install xserver-xorg xorg Thank you. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Lauren found her dream laptop. Find the PC that’s right for you. http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533565: linux-image-2.6.30-1-686: ATA bus error messages for PATA_SCH module
Package: linux-image-2.6.30-1-686
Version: 2.6.30-1
Severity: normal
am using Debian 5.0 with 2.6.30 kernel. I see the following messages during
kernel boot. Here is the relevant dmesg output:
[ 4.368333] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 4.368424] ata1.00: BMDMA stat 0x24
[ 4.368511] ata1.00: cmd c8/00:80:59:0d:4c/00:00:00:00:00/e2 tag 0 dma 65536 in
[ 4.368515] res 51/84:00:d8:0d:4c/00:00:00:00:00/e2 Emask 0x10 (ATA bus error)
[ 4.368715] ata1.00: status: { DRDY ERR }
[ 4.368790] ata1.00: error: { ICRC ABRT }
[ 4.368892] ata1: soft resetting link
[ 4.553143] ata1.00: configured for UDMA/100
[ 4.553231] ata1: EH complete
[ 4.567926] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 4.568024] ata1.00: BMDMA stat 0x24
[ 4.568119] ata1.00: cmd c8/00:80:59:0d:4c/00:00:00:00:00/e2 tag 0 dma 65536 in
[ 4.568122] res 51/84:00:d8:0d:4c/00:00:00:00:00/e2 Emask 0x10 (ATA bus error)
[ 4.568323] ata1.00: status: { DRDY ERR }
[ 4.568398] ata1.00: error: { ICRC ABRT }
[ 4.568493] ata1: soft resetting link
[ 4.753342] ata1.00: configured for UDMA/100
[ 4.753427] ata1: EH complete
and 3-4 more exact repetitions of the above messages.
I just have a single IDE drive attached and the IDE driver that is loaded is:
CONFIG_PATA_SCH.
What does the above error message mean? Also I see these error messages on all
the recent kernels - 2.6.26, 2.6.28, 2.6.29 and 2.6.30.
Please let me know if you need output of additional things.
-- Package-specific info:
** Version:
Linux version 2.6.30-1-686 (Debian 2.6.30-1) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-11) ) #1 SMP Sun Jun 14 16:11:32 UTC 2009
** Command line:
root=/dev/sda1 ro quiet
** Not tainted
** Kernel log:
[4.759319] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[4.759387] ata1.00: BMDMA stat 0x24
[4.759456] ata1.00: cmd c8/00:20:9f:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[4.759460] res 51/84:00:be:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[4.759589] ata1.00: status: { DRDY ERR }
[4.759666] ata1.00: error: { ICRC ABRT }
[4.759762] ata1: soft resetting link
[4.928451] ata1.00: configured for UDMA/100
[4.928476] ata1: EH complete
[4.933670] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[4.933758] ata1.00: BMDMA stat 0x24
[4.933846] ata1.00: cmd c8/00:20:9f:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[4.933850] res 51/84:00:be:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[4.934052] ata1.00: status: { DRDY ERR }
[4.934128] ata1.00: error: { ICRC ABRT }
[4.934224] ata1: soft resetting link
[5.104446] ata1.00: configured for UDMA/100
[5.104470] ata1: EH complete
[5.108031] ata1.00: limiting speed to UDMA/66:PIO4
[5.108041] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[5.108139] ata1.00: BMDMA stat 0x24
[5.108227] ata1.00: cmd c8/00:20:9f:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[5.108231] res 51/84:00:be:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[5.108433] ata1.00: status: { DRDY ERR }
[5.108509] ata1.00: error: { ICRC ABRT }
[5.108605] ata1: soft resetting link
[5.280433] ata1.00: configured for UDMA/66
[5.280449] ata1: EH complete
[5.304192] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[5.304280] ata1.00: BMDMA stat 0x24
[5.304368] ata1.00: cmd c8/00:20:bf:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[5.304372] res 51/84:00:de:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[5.304574] ata1.00: status: { DRDY ERR }
[5.304650] ata1.00: error: { ICRC ABRT }
[5.304748] ata1: soft resetting link
[5.476450] ata1.00: configured for UDMA/66
[5.476471] ata1: EH complete
[5.481870] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[5.481958] ata1.00: BMDMA stat 0x24
[5.482045] ata1.00: cmd c8/00:20:bf:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[5.482049] res 51/84:00:de:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[5.482251] ata1.00: status: { DRDY ERR }
[5.482327] ata1.00: error: { ICRC ABRT }
[5.482423] ata1: soft resetting link
[5.652447] ata1.00: configured for UDMA/66
[5.652462] ata1: EH complete
[5.656215] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[5.656299] ata1.00: BMDMA stat 0x24
[5.656386] ata1.00: cmd c8/00:20:bf:4a:56/00:00:00:00:00/e1 tag 0 dma 16384
in
[5.656390] res 51/84:00:de:4a:56/00:00:00:00:00/e1 Emask 0x10 (ATA
bus error)
[5.656591] ata1.00: status: { DRDY ERR }
[5.656667] ata1.00: error: { ICRC ABRT }
[5.656762] ata1: soft resetting link
[5.828433] ata1.00: configured for UDMA/66
[5.828454] ata1: EH complete
[5.830561] ata1.00: limiting speed to UDMA/33:PIO4
[5.830570] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[5.830656] ata1.00: BMDMA stat 0x24
[5.830743] ata1.00: cmd
Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500)
Package: wnpp Severity: wishlist Owner: Kushal Koolwal kushalkool...@hotmail.com * Package name: xserver-xorg-video-psb Version : 1.0 Upstream Author : Intel Moblin * URL : http://www.intel.com/products/mid/ * License : GPL Programming Lang: C/C++ Description : Xorg Graphics driver for Intel Poulsbo chipset (GMA 500) http://lists.debian.org/debian-devel/2009/06/msg00515.html -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500)
Thanks Daniel! Sorry about the errors in the ITP (license, versions). I did an ITP for the first time and I wasn't quite sure how to find proper licenses and versions. Does it need to be corrected? If yes, then how? I apologize for the trouble and errors. Kushal Koolwal I do blog at http://blogs.koolwal.net/ Subject: Bug#533450: ITP: xserver-xorg-video-psb -- Xorg Graphics driver for Intel Poulsbo chipset (GMA 500) Date: Wed, 17 Jun 2009 12:02:16 -0700 From: dmoer...@gmail.com To: kushalkool...@hotmail.com; 533...@bugs.debian.org CC: debian-de...@lists.debian.org I originally just sent this to debian-devel since I didn't see the bug report on it, here are my comments on the bug report for posterity. I'll keep debian-devel on CC. I've attached the forwarded message at the end. On Wed, Jun 17, 2009 at 11:20 AM, Kushal Koolwal wrote: * Package name: xserver-xorg-video-psb Version : 1.0 I only see version 0.2.1 on various websites, the upstream git repo on moblin.org no longer exists. Upstream Author : Intel Moblin * URL : http://www.intel.com/products/mid/ * License : GPL It looks like MIT to me. Programming Lang: C/C++ Description : Xorg Graphics driver for Intel Poulsbo chipset (GMA 500) http://lists.debian.org/debian-devel/2009/06/msg00515.html -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Here was my original message that I sent out before I saw the bug report: -- Forwarded message -- From: Daniel Moerner Date: Wed, Jun 17, 2009 at 11:42 AM Subject: Re: Intel Atom Poulsbo chipset Xorg driver in Debian To: debian-de...@lists.debian.org On Wed, Jun 17, 2009 at 10:49 AM, Jonathan Wiltshire wrote: On Wed, Jun 17, 2009 at 10:42:55AM -0700, Kushal Koolwal wrote: It seems that the support for Intel's Poulsbo chipset (Graphics GMA 500) for Atom processor (US15) is sparse [1]. So far I have been able to find a driver package in Ubuntu Hardy [2]. I was wondering if anyone has ideas as to if Debian will get the support for Poulsbo chipset. From a brief look at the package in Hardy, the license would be considered free, so I suggest you file a Request for Packaging [1] and hopefully somebody will take you up on it. Is the driver in better shape than it was in January? http://www.happyassassin.net/2009/01/30/intel-gma-500-poulsbo-graphics-on-linux-a-precise-and-comprehensive-summary-as-to-why-youre-screwed/ Ubuntu even requested to have it removed from their archive because it was obsolete and broken: https://launchpad.net/ubuntu/+source/xserver-xorg-video-psb/0.2.1-1ubuntu3 I'm not sure if this is something that would be wanted in the archive unless support has improved (which is a legitimate possibility, given that Dell purports to support this chipset in the Mini 12). Cheers, Daniel -- Daniel Moerner _ Lauren found her dream laptop. Find the PC that’s right for you. http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519038: FW: Bug#519038: lm-sensors: dme1737 does not honour sensors3.conf settings
What are you expecting? Ah..I see what happened. In Linux kernel the support for my chipset, SCH3114, is contained inside dme1737 module. So the module dme1737 has to be loaded to get output from sensors. Since there is no specific settings for SCH311X in sensors3.conf I thought may be the settings of dme1737 in sensors3.conf should work because that is the required module. However, I got it working by adding the following files to my sensors3.conf file. chip sch311x-isa-* # Temperature inputs label temp1 CPU Temp label temp2 M/B Temp label temp3 Unknown or better just adding sch311x-isa-* after chip dme1737-* also works fine. Thank you for the hint. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518096: watchdog: wd_keepalive breaks the functionality
Please close this bug. On a freshly installed system, all worked fine. Still not able to figure out what went wrong on the existing installation. Thanks Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: Life without walls. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1a_explore_032009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519038: lm-sensors: dme1737 does not honour sensors3.conf settings
Package: lm-sensors Version: 1:3.0.2-1+b2 Severity: minor I tried modifying the settings for my dme1737 module in /etc/sensors3.conf file like this: *** chip dme1737-* # Temperature inputs label temp1 CPU Temp label temp2 M/B Temp label temp3 Unknwon *** But in my output (sensors) the label names (CPU Temp M/B Temp) does not appear. Here is my sensors output: *** debian-486:~# sensors sch311x-isa-0c70 Adapter: ISA adapter in0: +5.27 V (min = +0.00 V, max = +6.64 V) in1: +1.87 V (min = +0.00 V, max = +2.99 V) in2: +3.27 V (min = +0.00 V, max = +4.38 V) in3: +4.92 V (min = +4.69 V, max = +5.18 V) in4:+11.97 V (min = +0.00 V, max = +15.94 V) in5: +3.27 V (min = +0.00 V, max = +4.38 V) in6: +2.92 V (min = +0.00 V, max = +4.38 V) fan1: 0 RPM (min =0 RPM) fan2: 0 RPM (min =0 RPM) fan3: 0 RPM (min =0 RPM) temp1: +54.2°C (low = -127.0°C, high = +127.0°C) temp2: +28.8°C (low = -127.0°C, high = +127.0°C) temp3: FAULT (low = -127.0°C, high = +127.0°C) ALARM cpu0_vid: +0.000 V *** -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.26-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lm-sensors depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libsensors4 1:3.0.2-1+b2 library to read temperature/voltag ii perl5.10.0-19Larry Wall's Practical Extraction ii sed 4.1.5-6 The GNU sed stream editor lm-sensors recommends no packages. Versions of packages lm-sensors suggests: pn i2c-tools none (no description available) pn read-edid none (no description available) pn sensord none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518096: watchdog: wd_keepalive breaks the functionality
Could you please check whether watchdog is really running and whether wd_keepalive was really stopped? Yes, only watchdog is running. debian:~# ps -ef | grep watch root 2846 1 0 12:35 ?00:00:00 /usr/sbin/watchdog root 2952 2846 0 12:43 ?00:00:00 [watchdog] root 2954 2895 0 12:43 pts/000:00:00 grep watch debian:~# debian:~# ps -ef | grep wd_keepalive root 2962 2895 0 12:44 pts/000:00:00 grep wd_keepalive debian:~# If you happen to have a system without either one running you could try getting more info by replacing --quiet with --verbose in the start-stop-daemon calls in /etc/init.d/watchdog. There also should be more information in the corrsponfing syslog file. I enabled the --verbose option and here is what I get in syslog upon system starts: Mar 4 12:45:19 debian watchdog[2846]: stopping daemon (5.4) Mar 4 12:45:19 debian wd_keepalive[3004]: starting watchdog keepalive daemon (5.4): int=10 alive=(null) realtime=yes Mar 4 12:45:19 debian wd_keepalive[3004]: stopping watchdog keepalive daemon (5.4) Mar 4 12:46:22 debian watchdog[2850]: starting daemon (5.4): Mar 4 12:46:22 debian watchdog[2850]: int=10s realtime=yes sync=no soft=no mla=0 mem=0 Mar 4 12:46:22 debian watchdog[2850]: ping: 192.168.0.101 Mar 4 12:46:22 debian watchdog[2850]: file: no file to check Mar 4 12:46:22 debian watchdog[2850]: pidfile: no server process to check Mar 4 12:46:22 debian watchdog[2850]: interface: no interface to check Mar 4 12:46:22 debian watchdog[2850]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Mar 4 12:47:10 debian watchdog[2850]: stopping daemon (5.4) Mar 4 12:47:10 debian wd_keepalive[2925]: starting watchdog keepalive daemon (5.4): int=10 alive=(null) realtime=yes Mar 4 12:47:10 debian wd_keepalive[2925]: stopping watchdog keepalive daemon (5.4) Mar 4 12:48:10 debian watchdog[2855]: starting daemon (5.4): Mar 4 12:48:10 debian watchdog[2855]: int=10s realtime=yes sync=no soft=no mla=0 mem=0 Mar 4 12:48:10 debian watchdog[2855]: ping: 192.168.0.101 Mar 4 12:48:10 debian watchdog[2855]: file: no file to check Mar 4 12:48:10 debian watchdog[2855]: pidfile: no server process to check Mar 4 12:48:10 debian watchdog[2855]: interface: no interface to check Mar 4 12:48:10 debian watchdog[2855]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no And here is the syslog output on Debian Etch: Mar 4 12:46:18 debian watchdog[2706]: stopping daemon (5.2) Mar 4 12:47:17 debian watchdog[2708]: starting daemon (5.2): Mar 4 12:47:17 debian watchdog[2708]: int=10s realtime=yes sync=no soft=no mla=3 mem=0 Mar 4 12:47:17 debian watchdog[2708]: ping: 192.168.0.101 Mar 4 12:47:17 debian watchdog[2708]: file: no file to check Mar 4 12:47:17 debian watchdog[2708]: pidfile: no server process to check Mar 4 12:47:17 debian watchdog[2708]: interface: no interface to check Mar 4 12:47:17 debian watchdog[2708]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Mar 4 12:47:54 debian watchdog[2708]: stopping daemon (5.2) Mar 4 12:48:54 debian watchdog[2705]: starting daemon (5.2): Mar 4 12:48:54 debian watchdog[2705]: int=10s realtime=yes sync=no soft=no mla=3 mem=0 Mar 4 12:48:54 debian watchdog[2705]: ping: 192.168.0.101 Mar 4 12:48:54 debian watchdog[2705]: file: no file to check Mar 4 12:48:54 debian watchdog[2705]: pidfile: no server process to check Mar 4 12:48:54 debian watchdog[2705]: interface: no interface to check Mar 4 12:48:54 debian watchdog[2705]: test=none(0) repair=none alive=none heartbeat=none temp=none to=root no_act=no Also I installed the watchdog package from Etch on my Lenny system, and it seems to works well. As soon as I upgrade to Lenny's watchdog package, it fails to function as mentioned initially. Please let me know if you need more information. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™ Contacts: Organize your contact list. http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518087: Removing libesd-alsa0 removes entire GNOME
Package: libesd-alsa0 Version: 0.2.36-3 Severity: normal Installed libesd-alsa0 package so that I can use XMMS2 along with GNOME sounds. Now when I try to remove libesd-alsa0 package, apt-get tries to uninstall the entire GNOME. Please see the output below: debian:/home/user# apt-get purge libesd-alsa0 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libenchant1c2a libmalaga7 iso-codes python-gtksourceview2 libsensors-applet-plugin0 gedit-common libgnomeprint2.2-data libgtksourceview2.0-common libgtksourceview2.0-0 libxtst6 libvoikko1 libgnomeprint2.2-0 libgnomeprintui2.2-0 libaspell15 libgnomeprintui2.2-common libgnomecups1.0-1 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: alacarte* eog* esound* gedit* gnome-about* gnome-applets* gnome-control-center* gnome-core* gnome-media* gnome-mount* gnome-panel* gnome-session* gnome-settings-daemon* gnome-terminal* gnome-utils* gnome-volume-manager* libbonoboui2-0* libebook1.2-9* libecal1.2-7* libedataserverui1.2-8* libeel2-2.20* libesd-alsa0* libgnome-desktop-2* libgnome-media0* libgnome-window-settings1* libgnome2-0* libgnomeui-0* libpanel-applet2-0* libslab0* nautilus* python-gnome2* sensors-applet* vino* yelp* 0 upgraded, 0 newly installed, 34 to remove and 0 not upgraded. After this operation, 49.1MB disk space will be freed. Do you want to continue [Y/n]? -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.28-versalogic-intelm (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libesd-alsa0 depends on: ii esound-common 0.2.36-3 Enlightened Sound Daemon - Common ii libasound21.0.16-2 ALSA library ii libaudiofile0 0.2.6-7Open-source version of SGI's audio ii libc6 2.7-18 GNU C Library: Shared libraries Versions of packages libesd-alsa0 recommends: pn esound-clientsnone (no description available) Versions of packages libesd-alsa0 suggests: ii esound0.2.36-3 Enlightened Sound Daemon - Support -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518096: watchdog: wd_keepalive breaks the functionality
Package: watchdog Version: 5.4-10 Severity: important I am using the AMD Geode Hardware watchdog driver geodewdt (CONFIG_GEODE_WDT) in Linux kernel. My /etc/modules contains the line: geodewdt which causes the module to load properly - /dev/watchdog file created. My /etc/watchdog.conf file has following line: ping192.168.0.101 However upon boot, I see some messages like: Starting watchdog keepalive daemon: Ignoring config line: ping 192.168.0.101 wd_keepalive Then I see, Stopping watchdog keepalive daemon Starting watchdog daemon. Although the wd_keepalive stops, somehow my ping line in still ignored. I verified this my shutting down the 192.168.0.101 machine and still after 1 minute my system does not reboot which it should. If use Etch on the same machine (with same kernel), watchdog version in Etch, everything works fine. The system shutsdown after 1 min from 101 going down. I guess watchdog version in Etch did not have wd_keepalive binary then. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.28-l6r200-test2 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages watchdog depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-18 GNU C Library: Shared libraries ii makedev 2.3.1-88 creates device files in /dev ii udev 0.125-7/dev/ and hotplug management daemo watchdog recommends no packages. watchdog suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517114: debian-installer: preseeding not working
Package: debian-installer Version: 20090123 Severity: important I tried installing Emdebian Grip 1.0 using the preseeding method suggested at: http://buildd.emdebian.org/grip/ and the preseeding fails in two ways: 1. First, you do not get a screen (after network detection) which asks you to enter the url of preseeding. http://lists.debian.org/debian-embedded/2009/02/msg00135.html 2. Even if you pass boot parameters at command line (url=), the preseeding still fails. http://lists.debian.org/debian-embedded/2009/02/msg00145.html The Debian Lenny documentation mentions about preseeding - Either we shold remove it from the docs or get it fixed in next stable update. Thanks -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-vl-deb-ws (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517158: linux-source-2.6.28: PGP .sign file remained in sources
Package: linux-source-2.6.28 Version: 2.6.28-1 Severity: minor Not sure if this is intential or not, but after unpacking linux-source-2.6.28, I found a file patch-2.6.28.5-6.bz2.sign in the root of source directory. Never saw this in previous kernel sources - so just thought to report it. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-vl-deb-ws (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.28 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co Versions of packages linux-source-2.6.28 recommends: ii gcc 4:4.3.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-18 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.28 suggests: ii kernel-package11.015 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20081213-1 developer's libraries and docs for ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516373:
Sorry the last mail somehow was incomplete. I am resending the links again Screenshot with high load immediately after resuming from suspend: http://blogs.koolwal.net/wp-content/uploads/Highload.png Screenshot of my idle system (normal load): http://blogs.koolwal.net/wp-content/uploads/Normal.png Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ It’s the same Hotmail®. If by “same” you mean up to 70% faster. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Same_022009
Bug#516373:
During this time, are there any processes sucking up the CPU? Here is a screenshot when the load is really high - it was a top output also: http://blogs.koolwal.net/wp-content/uploads/Highload.png Even you can see the high load (Red rectangle) up in the GNOME applet (using System monitor) Here is a screenshot when my laptop is functioning normally - with load _ Windows Live™: Discover 10 secrets about the new Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!7540.entry?ocid=TXT_TAGLM_WL_t2_ugc_post_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516373: gnome-power-manager: High System Load (upto 8) on resuming from suspend
Package: gnome-power-manager Version: 2.22.1-4 Severity: normal Whenever I resume my computer from Suspend mode, I see (using top or htop) that the System load goes really high - usually upto 8. Then slowly it starts getting low and usually takes about a minute and a half to come to normal (idle) system load which for my machine is usually 1. I put my computer to suspend mode by going to System-Shutdown-Suspend under GNOME. Please let me know if you need more information. -- Package-specific info: Distro version: 5.0 Kernel version: 2.6.26-1-686 g-p-m version:open 'gnome-power-manager HAL version: 0.5.11 System manufacturer: missing System version: missing System product: missing AC adapter present: yes Battery present: yes Laptop panel present: yes CPU scaling present: no Battery Information: battery.charge_level.current = 52812 (0xce4c) (int) battery.charge_level.design = 56160 (0xdb60) (int) battery.charge_level.last_full = 56160 (0xdb60) (int) battery.charge_level.percentage = 94 (0x5e) (int) battery.charge_level.rate = 0 (0x0) (int) battery.is_rechargeable = true (bool) battery.model = 'CP257410-XX / CP257411-XX' (string) battery.present = true (bool) battery.rechargeable.is_charging = false (bool) battery.rechargeable.is_discharging = true (bool) battery.reporting.current = 4890 (0x131a) (int) battery.reporting.design = 5200 (0x1450) (int) battery.reporting.last_full = 5200 (0x1450) (int) battery.reporting.rate = 0 (0x0) (int) battery.reporting.technology = 'Li-ion' (string) battery.reporting.unit = 'mAh' (string) battery.serial = '1' (string) battery.technology = 'lithium-ion' (string) battery.type = 'primary' (string) battery.vendor = 'Fujitsu' (string) battery.voltage.current = 12192 (0x2fa0) (int) battery.voltage.design = 10800 (0x2a30) (int) battery.voltage.unit = 'mV' (string) GNOME Power Manager Process Information: root 15987 0.0 0.1 3864 1200 tty1 R+ 16:09 0:00 \_ /bin/sh /usr/share/gnome-power-manager/gnome-po root 3574 0.0 1.0 26036 10820 ?Ss 09:06 0:00 gnome-power-manager root 3651 0.0 0.9 4 9356 ?S09:06 0:00 /usr/lib/gnome-power-manager/gnome-inhibit-applet --oaf-activat root 3674 0.0 0.9 0 9240 ?S09:06 0:00 /usr/lib/gnome-power-manager/gnome-brightness-applet --oaf-acti HAL Process Information: 101 2954 0.0 0.3 6080 3864 ?Ss 09:01 0:00 /usr/sbin/hald root 2955 0.0 0.1 3320 1084 ?S09:01 0:00 \_ hald-runner root 2978 0.0 0.1 3384 1040 ?S09:01 0:00 \_ hald-addon-input: Listening on /dev/input/event1 /dev/i 101 2987 0.0 0.0 2272 880 ?S09:01 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acp root 2988 0.0 0.1 3384 1040 ?S09:01 0:01 \_ hald-addon-storage: polling /dev/hda (every 2 sec) -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-power-manager depends on: ii dbus-x11 1.2.1-5 simple interprocess messaging syst ii gconf2 2.22.0-1 GNOME configuration database syste ii hal0.5.11-8 Hardware Abstraction Layer ii libart-2.0-2 2.3.20-2 Library of functions for 2D graphi ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.22.0-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.22.0-1 The Bonobo UI library ii libc6 2.7-18GNU C Library: Shared libraries ii libcairo2 1.6.4-7 The Cairo 2D vector graphics libra ii libdbus-1-31.2.1-5 simple interprocess messaging syst ii libdbus-glib-1-2 0.76-1simple interprocess messaging syst ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libgconf2-42.22.0-1 GNOME configuration database syste ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgnome-keyring0 2.22.3-2 GNOME keyring services library ii libgnome2-02.20.1.1-1The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.20.1.1-1A powerful object-oriented display ii libgnomeui-0 2.20.1.1-2The GNOME 2 libraries (User Interf ii libgnomevfs2-0 1:2.22.0-5GNOME Virtual File System
Bug#378546: Excessive Memory usage by kaxel-kapt
hi, I am facing the exact same problem with axel-kapt - The application brings down the system to crawl and System monitors shows that 98% of memory used by programs instead of 5-10% when axel-kapt is not running. Even opening a gnome-terminal windows takes 5-10 seconds. Running kaptain does not consumes the memory but no GUI pops-up. I am using Debian Lenny (5.0) with 2.6.26-1-686 kernel Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Stay up to date on your PC, the Web, and your mobile phone with Windows Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516053: jigdo: Cannot use Jigdo to download ISO files
Package: jigdo Version: 0.7.3-2 Severity: normal I understand that right now Jigdo is not capable of downloading .jigdo files but according to the package description it should still be possible to download ISO image files? I tried download certain ISO image files but jigdo is never able to complete the download. When the process interrrupts it does not automatically resumes downloading. Thanks -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-vl-deb-ws (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages jigdo depends on: ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.7-18GNU C Library: Shared libraries ii libcairo2 1.6.4-7 The Cairo 2D vector graphics libra ii libcurl3-gnutls7.18.2-8 Multi-protocol file transfer libra ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libgcc11:4.3.2-1.1 GCC support library ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libgtk2.0-02.12.11-4 The GTK+ graphical user interface ii libpango1.0-0 1.20.5-3 Layout and rendering of internatio ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime jigdo recommends no packages. Versions of packages jigdo suggests: ii jigdo-file0.7.3-2Download Debian CD images from any -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515052:
Hi Tim, So I made some progress after downloading the latest 0.9.6 version as suggested by you. But now I got stuck at the ksplice-apply command. Here is what I get: make: Entering directory `/usr/src/linux-headers-2.6.26-ksplice' INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi.ko INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux-helper.ko INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux.ko make: Leaving directory `/usr/src/linux-headers-2.6.26-ksplice' Ksplice update tarball written to ksplice-kkda1whi.tar.gz debian-sid:/usr/src/linux-source-2.6.26/kernel# ksplice-apply ./ksplice-kkda1whi.tar.gz Error applying Ksplice update kkda1whi: Ksplice has aborted the upgrade because Ksplice has been unable to match the object code produced by your current compiler and assembler against the running kernel's object code. If you provided the exact kernel source to the running kernel, then it appears that your current compiler and/or assembler are behaving differently from the compiler and assembler used to build the running kernel. If possible, please use the exact compiler and assembler that were used to build the running kernel. If you are using exactly the same compiler and assembler, consider reporting a bug to de...@ksplice.com. Died at /usr/local/sbin/ksplice-apply line 131. debian-sid:/usr/src/linux-source-2.6.26/kernel# Now the ksplice-create commands is able to successfully create the tarball file. I am pretty sure that the kernel that I am using (2.6.26-ksplice) is compiled with the same gcc version on my system. Here is what I did to ensure that: 0. apt-get update; apt-get upgrade 1. I just downloaded the linux-source-2.6.26 from Debian Sid. 2. Copied my default /boot/config-2.6.26-1-686 to the sources linux-source-2.6.26 3. Compiled a new kernel called 2.6.26-ksplice (make-kpkg way) And then I followed the instructions as mentioned in my original bug report. Not sure if I missed any step or there is still some bug. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Faster_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515052:
Hi Tim, Are you running the kernel 2.6.26-ksplice as well as using it to be build your update against? Yes, I was running 2.6.26-ksplice while doing ksplice-create and ksplice-apply process. Sorry I forgot to mentioned that in the steps previously listed. If you send me the data stored in the debugging file when your run ksplice-apply with debugging enabled Not sure where the debug output is stored, but I am attaching the debug messages from dmesg when I gave the command ksplice-apply --debug ./ksplice-kkda1whi.tar.gz Please see the attachment. Thank you once again for your prompt response. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 ksplice.debug Description: Binary data
Bug#515052:
Yes, it somehow got compiled with Quoth... when I was trying different thing - like re-compiling kernel with default config file when my previous attempt to use ksplice-create failed as mentioned before. So in order to distinguish the process I deleted the source (2.6.26) in which Quoth.. was compiled and I downloaded the a fresh copy of source again and this time I slightly modified the patch from the example to replace Quoth with Quote so that I know if the process worked or not. I guess may be this is too much confusingsorry about that. Should I just start fresh and see what happens? Thanks Kushal Koolwal I do blog at http://blogs.koolwal.net/ Date: Fri, 13 Feb 2009 17:06:25 -0500 From: tabb...@mit.edu To: kushalkool...@hotmail.com CC: 515...@bugs.debian.org Subject: RE: Bug#515052: From looking at the debugging output, I'm guessing that the 2.6.26-ksplice kernel that you compiled was compiled with the Quoth the kernel example patch already applied. You should be able to confirm this fairly easily by seeing whether Quoth the kernel appears in the output of dmesg. -Tim Abbott On Fri, 13 Feb 2009, Kushal Koolwal wrote: Hi Tim, Are you running the kernel 2.6.26-ksplice as well as using it to be build your update against? Yes, I was running 2.6.26-ksplice while doing ksplice-create and ksplice-apply process. Sorry I forgot to mentioned that in the steps previously listed. If you send me the data stored in the debugging file when your run ksplice-apply with debugging enabled Not sure where the debug output is stored, but I am attaching the debug messages from dmesg when I gave the command ksplice-apply --debug ./ksplice-kkda1whi.tar.gz Please see the attachment. Thank you once again for your prompt response. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515052:
Hello, After starting from scratch, the process just worked fine. I think this bug is resolved. Thank you very much for your co-operation and patience. Really appreciate it. Ksplice is a big leap for Linux kernel advancement. Kushal Koolwal I do blog at http://blogs.koolwal.net/ Date: Fri, 13 Feb 2009 17:42:36 -0500 From: tabb...@mit.edu To: kushalkool...@hotmail.com CC: 515...@bugs.debian.org Subject: RE: Bug#515052: On Fri, 13 Feb 2009, Kushal Koolwal wrote: Yes, it somehow got compiled with Quoth... when I was trying different thing - like re-compiling kernel with default config file when my previous attempt to use ksplice-create failed as mentioned before. So in order to distinguish the process I deleted the source (2.6.26) in which Quoth.. was compiled and I downloaded the a fresh copy of source again and this time I slightly modified the patch from the example to replace Quoth with Quote so that I know if the process worked or not. I guess may be this is too much confusingsorry about that. Right, well the problem is that Ksplice requires that you give it precisely the running kernel source, and you gave it the running kernel source without the Quoth patch applied. So, one of Ksplice's safety checks aborted the upgrade. It should work if you were to use the correct running kernel source and have your patch change Quoth to Quote. Should I just start fresh and see what happens? That might be easiest. -Tim Abbott _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515052: ksplice-create fails to create tarball
Package: ksplice
Version: 0.9.5-1
Severity: important
I was trying to follow the example at:
http://www.ksplice.com/example-update
This is what I did so far:
#cd /usr/src/
#apt-get install linux-source-2.6.26
#tar -xjvf linux-source-2.6.26.tar.bz2
#cd linux-source-2.6.26
#cp /boot/config-2.6.26-1-686 .config
#make xconfig
#mkdir ksplice
#cd ksplice/
#cp /boot/config-2.6.26-1-686 .config
#cp /boot/System.map-2.6.26-1-686 System.map
#ln -s /lib/modules/2.6.26-1-686/build
/usr/src/linux-source-2.6.26/ksplice/build
#cd ../kernel
#pwd
/usr/src/linux-source-2.6.26/kernel
#ksplice-create --patch=printk.patch /usr/src/linux-source-2.6.26
The first error message that I got was:
In file included from include/linux/gfp.h:4,
from include/linux/slab.h:12,
from include/linux/percpu.h:5,
from include/asm/local.h:4,
from include/linux/module.h:19,
from init/main.c:13:
include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or directory
include/linux/mmzone.h:197:5: warning: MAX_NR_ZONES is not defined
Then after searching on Internet I found that I need to give:
#make prepare
After doing the above, now I get the following error message:
#ksplice-create --patch=printk.patch /usr/src/linux-source-2.6.26
Starting kernel builds (this process might take a long time)...
scripts/kconfig/conf -s arch/x86/Kconfig
rm ksplice-revert-stamp
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CC init/main.o
/bin/sh: scripts/genksyms/genksyms: No such file or directory
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
Aborting: Prebuild failed at /usr/bin/ksplice-create line 180.
debian-sid:/usr/src/linux-source-2.6.26/kernel#
All the commands that I gave start with # symbol. Also I am attaching my
printk.patch file below:
--- linux-source-2.6.26/kernel/printk.c 2009-02-12 15:13:57.0 -0800
+++ linux-test/kernel/printk_patch.c2009-02-12 15:17:45.0 -0800
@@ -610,7 +610,8 @@
{
va_list args;
int r;
-
+
+ vprintk(Quoth the kernel:\n, NULL);
va_start(args, fmt);
r = vprintk(fmt, args);
va_end(args);
Thanks
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ksplice depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii gcc [c-compiler]4:4.3.2-3The GNU C compiler
ii gcc-4.1 [c-compiler 4.1.2-25 The GNU C compiler
ii gcc-4.2 [c-compiler 4.2.4-6 The GNU C compiler
ii gcc-4.3 [c-compiler 4.3.3-3 The GNU C compiler
ii libc6 2.7-18 GNU C Library: Shared libraries
ii patch 2.5.9-5 Apply a diff file to an original
ii perl5.10.0-19Larry Wall's Practical Extraction
ii rsync 3.0.5-1 fast remote file copy program (lik
ksplice recommends no packages.
ksplice suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515052: ksplice-create fails to create tarball
Ok thanks. I will try the upstream version on Debian Sid. Kushal Koolwal I do blog at http://blogs.koolwal.net/ Date: Thu, 12 Feb 2009 19:49:22 -0500 From: tabb...@mit.edu To: kushalkool...@hotmail.com; 515...@bugs.debian.org Subject: Re: Bug#515052: ksplice-create fails to create tarball Hello, This problem is caused by a bug in Ksplice 0.9.5 that was fixed in the Ksplice 0.9.6 upstream release. -Tim Abbott _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009
Bug#512603:
Hi Daniel, Thanks for info. Two questions: 1. Also while searching other bug report on similar issue I found this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453105 So I installed the libesd-alsa0 package and I got my GNOME sound events and xmms2 sound back. Do you see any potential danger/conflict in using this approach? 2. If I go with pulseaudio approach (looks like this will replace esd based on above link) can I play my GNOME events and sounds from other media player (like xmms2) without having to install esd? Thanks for your help! Appreciate it. I do blog at http://blogs.koolwal.net/ _ Hotmail® goes where you go. On a PC, on the Web, on your phone. http://www.windowslive-hotmail.com/learnmore/versatility.aspx#mobile?ocid=TXT_TAGHM_WL_HM_versatility_121208 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512603: xmms2 fails with esound installed
Hi Thomas, I tried using pulse output plugin but no luck. Here is what I get: u...@debian:~$ killall xmms2d u...@debian:~$ xmms2d -o pulse INFO: ../src/xmms/log.c:36: Initialized logging system :) INFO: ../src/xmms/ipc.c:950: IPC listening on 'unix:///tmp/xmms-ipc-user'. INFO: ../src/xmms/main.c:507: Using output plugin: pulse u...@debian:~$ xmms2 add sound_test.mp3 Added sound_test.mp3 u...@debian:~$ xmms2 play INFO: ../src/xmms/xform.c:1461: Successfully setup chain for 'file:///usr/share/xmms2/mind.in.a.box-lament_snipplet.ogg' (1) containing file:magic:vorbis:segment ERROR: ../src/xmms/outputplugin.c:439: Could not open output .cache/xmms2/xmms2d.log (END) Also I tried libao plugin but again no luck. I get lots of error messages as soon as I tell xmms2d to use libao plugin. u...@debian:~$ killall xmms2d u...@debian:~$ xmms2d -o ao INFO: ../src/xmms/log.c:36: Initialized logging system :) INFO: ../src/xmms/ipc.c:950: IPC listening on 'unix:///tmp/xmms-ipc-user'. INFO: ../src/xmms/main.c:507: Using output plugin: ao ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ALSA snd_pcm_open error: Device or resource busy ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave Also I tried to look for some documentation which can explain to how to configure libao to use esd but I was not able to. Can you point me to it please? Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™ Hotmail®:…more than just e-mail. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_explore_012009
Bug#512595: xserver-xorg-video-intel: LVDS screen goes blank on starting X server
Package: xserver-xorg-video-intel Version: 2:2.3.2-2+lenny5 Severity: important My graphic chipset is: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) I primarily use a VGA monitor as my primary display device. Everything works fine with it. But as soon as I attached a secondary display device (a LVDS flat panel) the screen on LVDS goes blank as soon as X servers gets started (gdm kicks in). The VGA display is fine. Also as soon as I hit Alt-F1 to switch to first console, the display on LVDS comes back. I also noticed that this problem does not exits on 2.3.2-2+lenny4. Something got changed between 2.3.2-2+lenny4 and 2.3.2-2+lenny5 (the current one which I am using). So if I copy the intel_drv.so from 2.3.2-2+lenny4 package to my /usr/lib/xorg/modules/drivers/ directory and restart my X, the screen on LVDS is restored properly. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-04-23 10:34 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1718484 2009-01-08 19:11 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1077 2008-04-23 10:34 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 31409 2009-01-21 17:47 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-10) Current Operating System: Linux sysuser-xp 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 Build Date: 09 January 2009 02:57:16AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jan 21 17:47:47 2009 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) |--Input Device Configured Mouse (==) |--Input Device Generic Keyboard (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi does not exist. Entry deleted from font path. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry
Bug#512603: xmms2 fails with esound installed
Package: xmms2 Version: 0.5DrLecter-2 Severity: important xmms2 play music files (MP3) just fine when we don't have esound package installed. However as soon as we install esound xmms2 won't play songs and gives following error message in the xmms2d.log file: --- Starting new xmms2d --- INFO: ../src/xmms/log.c:36: Initialized logging system :) INFO: ../src/xmms/ipc.c:950: IPC listening on 'unix:///tmp/xmms-ipc-user'. INFO: ../src/xmms/main.c:507: Using output plugin: alsa ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave ERROR: ../src/plugins/alsa/alsa.c:213: Couldn't open device: default ERROR: ../src/xmms/output.c:957: Could not initialize output plugin ..cache/xmms2/xmms2d.log (END) I need esound package (esd utility) so that I can hear my GNOME events and sounds. Looks like esound takes control over alsa plugin and hence xmms2 fails. In xmms - pervious version of xmms2 I use to get around this by forcing xmms2 to use the libesdout.so output plugin and everything was happy - GNOME sound events and XMMS player. With XMMS2 I was not able to find a similar libesdout plugin. Thanks -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-ebx12-test5 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xmms2 depends on: ii xmms2-client-cli 0.5DrLecter-2 XMMS2 - cli client ii xmms2-core 0.5DrLecter-2 XMMS2 - core package ii xmms2-plugin-alsa 0.5DrLecter-2 XMMS2 - ALSA output ii xmms2-plugin-id3v2 0.5DrLecter-2 XMMS2 - ID3v2 plugin ii xmms2-plugin-mad 0.5DrLecter-2 XMMS2 - libmad based mp3 decoder ii xmms2-plugin-vorbis0.5DrLecter-2 XMMS2 - vorbis decoder xmms2 recommends no packages. xmms2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484545: Media Wiki Extension help
Hello, I would be interested in joining this. I have been using Debian for the past 3 years and I am pretty comfortable with it. Moreover I have done research projects on Web 2.0 (Wikis/blogs) and have a good understanding of these application and their uses. Looking forward to your response. I am really eager to contribute to the Debian community. If I get accepted this will be my first time joining the Debian community. Thanks Kushal Koolwal _ It’s a talkathon – but it’s not just talk. http://www.imtalkathon.com/?source=EML_WLH_Talkathon_JustTalk
Bug#474148: bootcd: Booting from USB CD-ROM support
Hello, I think I have found the solution to the problem. We need to tell the initramfs to include the driver for SCSI removal able device and all is fine. The file is /etc/initramfs/modules. Although it may not be a bad idea to include the sr driver in the bootcd-mkinitramfs package. Kushal Koolwal Subject: Bug#474148: bootcd: Booting from USB CD-ROM support From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Thu, 3 Apr 2008 03:32:57 -0700 Package: bootcd Version: 3.00 Severity: wishlist The bootcd package works great from an IDE CD-ROM but gives a Kernel Panic if I try to boot the CD from a USB CD-ROM. Is there any way by which we can hack the program to boot from a USB CD-ROM? Thanks in advance for your time. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.24 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages bootcd depends on: ii bootcd-i386 3.00 bootcd extension to create images ii cpio2.6-18 GNU cpio -- a program to manage ar ii dosfstools 2.11-2.1+b1 Utilities to create and check MS-D ii fdutils 5.5-20060227-1.1 Linux floppy utilities ii file4.17-5etch3 Determines file type using magic ii mkisofs 9:1.1.2-1Dummy transition package for genis ii realpath1.10 Return the canonicalized absolute Versions of packages bootcd recommends: pn cdrecord none (no description available) -- no debconf information It’s a talkathon – but it’s not just talk. Check out the i’m Talkathon. _ It’s a talkathon – but it’s not just talk. http://www.imtalkathon.com/?source=EML_WLH_Talkathon_JustTalk
Bug#474148: bootcd: Booting from USB CD-ROM support
Package: bootcd Version: 3.00 Severity: wishlist The bootcd package works great from an IDE CD-ROM but gives a Kernel Panic if I try to boot the CD from a USB CD-ROM. Is there any way by which we can hack the program to boot from a USB CD-ROM? Thanks in advance for your time. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.24 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages bootcd depends on: ii bootcd-i386 3.00 bootcd extension to create images ii cpio2.6-18 GNU cpio -- a program to manage ar ii dosfstools 2.11-2.1+b1 Utilities to create and check MS-D ii fdutils 5.5-20060227-1.1 Linux floppy utilities ii file4.17-5etch3 Determines file type using magic ii mkisofs 9:1.1.2-1Dummy transition package for genis ii realpath1.10 Return the canonicalized absolute Versions of packages bootcd recommends: pn cdrecord none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
