Re: Raising minimum CPU requirement for i386 kernel
On Sun, 24 May 2009, Bastian Blank wrote: This means that Debian will get uninstallable on the following CPUs: - Intel i486, There is new hardware sold today that is (only) compatible to the 486 SX instruction set. But it runs at 300 MHz. So it would be a pity to loose support for such hardware. http://www.dmp.com.tw/tech/Vortex86SX/ http://www.compactpc.com.tw/ebox-2300.htm Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raising minimum CPU requirement for i386 kernel
Hi, Bastian Blank schrieb: This means that Debian will get uninstallable on the following CPUs: - Intel i486, - Intel Pentium (MMX), - AMD K5, - AMD K6(-2, -3), Many schools are using LTSP on Debian (Edu) and have this hardware as their thinclients. Would be a shame if all those schools using free software cannot use the next release (and following) because their hardware is no longer supported. And I'm talking of really large numbers here worldwide. Regards, -- .''`. Philipp Hübner debala...@arcor.de : :' : pgp fp: BA61 0B0A 2626 D49C BFC6 1C18 1619 74E4 C259 E0E8 `. `'` HP: http://debalance.funpic.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Re: Raising minimum CPU requirement for i386 kernel
On Sun, May 24, 2009 at 9:07 PM, Bastian Blank wa...@debian.org wrote: - VIA C3 before Nehemiah and - National Semiconductor Geode (GXm, GXLV, GX1 and GX2). That affects XO-1 hardware being manufactured now, and C3s are among the viable CPUs for low cost, low dissipation school server style hardware. On the school server, I do my best to keep Debian a valid alternative (though the builds are Fedora based) and with a bit of packaging help most (all?) the XS specific packages could be in Debian. On the XO side, Jonas is packaging sugar and there's a mini-CDD called DebXO that seems to be quite active. I understand supporting additional hw does mean sizable work. Thanks for the fantastic work done so far. Please do consider not dropping support. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raising minimum CPU requirement for i386 kernel
On Sun, 24 May 2009, Bastian Blank wrote: Hi folks I would like to raise the minimum CPU requirement for the shipped Linux kernels in the i386 port to i686 (with cmov). [..] Popcon gives us some rough numbers to think about: linux-image-2.6-68649518 linux-image-2.6-486 6191 Given that the installer's automatic kernel choice tends to be accurate, we've got quite some non-cmov users. Actually, i386 has got many more non-cmov users than any non-i386/amd64 architecture has _in total_: linux-image-2.6-ixp4xx 772 (=arm/armel) linux-image-2.6-powerpc 551 linux-image-2.6-sparc64 192 linux-image-2.6-orion5x 106 (=arm/armel) (rest 100) #include popcon-accuracy-disclaimer.h So, the good work you're doing to keep supporting arm/powerpc/sparc/etc. will actually benefit much less users than the number you'll be annoying when you drop i386 non-cmov ... Best regards, Anne Bezemer -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529312: linux-image-2.6.26-2-686-bigmem: Does not recognize all CPUs on summit SMP machines
On Mon, May 18, 2009 at 05:04:53PM -0600, dann frazier wrote: A fix has been committed. It would be helpful if you could test a lenny snaphot build and confirm the fix. Information on installing snapshots is available here: http://wiki.debian.org/DebianKernel The version you will want to test will be = 2.6.26-16~snapshot.13633 and should be available after the next daily build cycle. Thank you very much for your extremely fast response. I've checked the wiki page and the repository it references. Also, I've checked the directory with the debs: http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/ Unfortunately, it appears the latest i386 lenny kernel snapshot is snapshot.13538 - all more recent ones are either not lenny or not i386. I'll continue to check and will report any success as soon as there will be a suitable kernel (lenny, i386, = 2.6.26-16~snapshot.13633) to test. With kind regards, -- Andreas Trottmann -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raising minimum CPU requirement for i386 kernel
J.A. Bezemer cos...@wormhole.robuust.nl writes: On Sun, 24 May 2009, Bastian Blank wrote: Hi folks I would like to raise the minimum CPU requirement for the shipped Linux kernels in the i386 port to i686 (with cmov). [..] Popcon gives us some rough numbers to think about: linux-image-2.6-68649518 linux-image-2.6-486 6191 Given that the installer's automatic kernel choice tends to be accurate, we've got quite some non-cmov users. Actually, i386 has got many more non-cmov users than any non-i386/amd64 architecture has _in total_: linux-image-2.6-ixp4xx 772 (=arm/armel) linux-image-2.6-powerpc 551 linux-image-2.6-sparc64 192 linux-image-2.6-orion5x 106 (=arm/armel) (rest 100) #include popcon-accuracy-disclaimer.h So, the good work you're doing to keep supporting arm/powerpc/sparc/etc. will actually benefit much less users than the number you'll be annoying when you drop i386 non-cmov ... Best regards, Anne Bezemer And how many people with such low power systems do run popcon? How many use a custom kernel? MfG Goswin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524571: Security update stable?
Did somebody could confirm that the security update of the kernel fix this? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raising minimum CPU requirement for i386 kernel
On Monday 25 May 2009, Goswin von Brederlow wrote: J.A. Bezemer cos...@wormhole.robuust.nl writes: On Sun, 24 May 2009, Bastian Blank wrote: Hi folks I would like to raise the minimum CPU requirement for the shipped Linux kernels in the i386 port to i686 (with cmov). [..] Popcon gives us some rough numbers to think about: linux-image-2.6-68649518 linux-image-2.6-486 6191 Given that the installer's automatic kernel choice tends to be accurate, we've got quite some non-cmov users. Actually, i386 has got many more non-cmov users than any non-i386/amd64 architecture has _in total_: linux-image-2.6-ixp4xx 772 (=arm/armel) linux-image-2.6-powerpc 551 linux-image-2.6-sparc64 192 linux-image-2.6-orion5x 106 (=arm/armel) (rest 100) #include popcon-accuracy-disclaimer.h So, the good work you're doing to keep supporting arm/powerpc/sparc/etc. will actually benefit much less users than the number you'll be annoying when you drop i386 non-cmov ... Best regards, Anne Bezemer And how many people with such low power systems do run popcon? How many use a custom kernel? MfG Goswin Quite a lot (me included) build an image once, and install it on multiple machines. I have about 60 machines built from three images for which this would be a problem. David -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Raising minimum CPU requirement for i386 kernel
On Mon May 25 2009 06:03:40 Goswin von Brederlow wrote: And how many people with such low power systems do run popcon? How many use a custom kernel? OTOH, none of the non-cmov i386 systems here run popcon either. --Mike Bird -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#530551: Wired network connection shuts down every 4-5min, then automaticaly restarts
Processing commands for cont...@bugs.debian.org: reassign 530551 linux-image-2.6.26-1-686 Bug#530551: Wired network connection shuts down every 4-5min, then automaticaly restarts Bug reassigned from package `base' to `linux-image-2.6.26-1-686'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530554: linux-image-2.6.29-2-686: hardware wlan kill switch state isn't restored correctly if put back off
Package: linux-image-2.6.29-2-686
Version: 2.6.29-4
Severity: normal
When using network-manager, I cannot connect to wifi if I reactivate wirelless
after having switched it off with the hardware kill-switch of my Dell Latitude
D820.
I noticed some weird things after trying to debug the cause of the problem.
I have the following kill-switch information appearing in /sys at boot if
kill-switch is off (meaning wireless activated) :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 1
/sys/devices/virtual/rfkill/rfkill1/state : 1
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 1
After I activate the kill-switch to disable networking, it gives :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 2
/sys/devices/virtual/rfkill/rfkill1/state : 2
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 2
However, after reactivating network (kill switch switched to off), I get only :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 1
/sys/devices/virtual/rfkill/rfkill1/state : 1
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 2
This probably explains the problem with network-manager (which is btw reflected
in the killswitch.state shown with lshal :
--- hal-on.log 2009-05-25 19:17:06.0 +0200
+++ hal-back-on.log 2009-05-25 19:20:01.0 +0200
@@ -80,18 +80,18 @@
udi = '/org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan'
info.addons.singleton = {'hald-addon-rfkill-killswitch'} (string list)
info.capabilities = {'killswitch'} (string list)
info.category = 'killswitch' (string)
info.interfaces = {'org.freedesktop.Hal.Device.KillSwitch'} (string list)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_4222' (string)
info.product = '3945ABG wlan Killswitch' (string)
info.subsystem = 'rfkill' (string)
info.udi = '/org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan'
(string)
info.vendor = 'Intel Corporation' (string)
killswitch.access_method = 'rfkill' (string)
killswitch.name = '3945ABG' (string)
- killswitch.state = 1 (0x1) (int)
+ killswitch.state = 2 (0x2) (int)
killswitch.type = 'wlan' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'rfkill' (string)
linux.sysfs_path =
'/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2' (string)
This used to work fine with Network-Manager over 2.6.26, though.
Thanks in advance.
-- Package-specific info:
** Version:
Linux version 2.6.29-2-686 (Debian 2.6.29-4) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-8) ) #1 SMP Sun May 3 12:46:00 UTC 2009
** Command line:
root=/dev/sda5 ro pci=assign-busses vga=791
** Tainted: P (1)
** Kernel log:
[ 10.456549] coretemp coretemp.0: Using relative temperature scale!
[ 10.472451] coretemp coretemp.1: Using relative temperature scale!
[ 14.423356] fuse init (API version 7.11)
[ 14.531429] kjournald starting. Commit interval 5 seconds
[ 14.546631] EXT3 FS on sda3, internal journal
[ 14.561588] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.611015] kjournald starting. Commit interval 5 seconds
[ 14.626346] EXT3 FS on dm-3, internal journal
[ 14.641141] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.685104] kjournald starting. Commit interval 5 seconds
[ 14.699952] EXT3 FS on dm-2, internal journal
[ 14.714364] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.752134] kjournald starting. Commit interval 5 seconds
[ 14.766460] EXT3 FS on dm-0, internal journal
[ 14.780224] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.841000] kjournald starting. Commit interval 5 seconds
[ 14.854725] EXT3 FS on dm-1, internal journal
[ 14.868207] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.013563] kjournald starting. Commit interval 5 seconds
[ 15.027303] EXT3 FS on dm-4, internal journal
[ 15.040477] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.141855] kjournald starting. Commit interval 5 seconds
[ 15.155362] EXT3 FS on dm-6, internal journal
[ 15.168501] EXT3-fs: mounted filesystem with ordered data mode.
[ 18.961074] kjournald starting. Commit interval 5 seconds
[ 18.974645] EXT3 FS on dm-5, internal journal
[ 18.987999] EXT3-fs: mounted filesystem with ordered data mode.
[ 22.853875] platform microcode: firmware: requesting intel-ucode/06-0f-02
[ 22.920562] platform microcode: firmware: requesting intel-ucode/06-0f-02
[ 22.942887] Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk,
Peter Oruba
[ 25.550273] NET: Registered protocol family 10
[ 25.564710] lo: Disabled Privacy Extensions
[ 52.027501] Bluetooth: L2CAP ver 2.11
[ 52.040834] Bluetooth: L2CAP
Re: Bug#530551: Wired network connection shuts down every 4-5min, then automaticaly restarts
reassign 530551 linux-image-2.6.26-1-686 thanks On Montag, 25. Mai 2009, Debian Bugs wrote: Package: base Version: 5.0 Every 4-5 minutes the wired network connection shuts down. After a couple of seconds it back on again. Log text: May 25 19:22:23 Slejpner kernel: [ 3266.373370] ACPI: PCI Interrupt :10:00.0[A] - GSI 17 (level, low) - IRQ 17 May 25 19:22:23 Slejpner kernel: [ 3266.373370] iwl3945: Radio disabled by HW RF Kill switch May 25 19:22:23 Slejpner kernel: [ 3266.373370] ACPI: PCI interrupt for device :10:00.0 disabled May 25 19:22:23 Slejpner pppd[4761]: Modem hangup May 25 19:22:23 Slejpner kernel: [ 3266.378069] eth0: late interrupt. May 25 19:22:23 Slejpner kernel: [ 3266.380211] b44: eth0: powering down PHY May 25 19:22:23 Slejpner pppd[4761]: Connect time 4.6 minutes. May 25 19:22:23 Slejpner pppd[4761]: Sent 273611 bytes, received 1097617 bytes. May 25 19:22:23 Slejpner pppd[4761]: Connection terminated. May 25 19:22:23 Slejpner kernel: [ 3266.547179] ACPI: PCI Interrupt :10:00.0[A] - GSI 17 (level, low) - IRQ 17 May 25 19:22:23 Slejpner kernel: [ 3266.547179] iwl3945: Radio disabled by HW RF Kill switch May 25 19:22:23 Slejpner kernel: [ 3266.547179] ACPI: PCI interrupt for device :10:00.0 disabled May 25 19:22:23 Slejpner kernel: [ 3266.553069] ADDRCONF(NETDEV_UP): eth0: link is not ready May 25 19:22:23 Slejpner kernel: [ 3266.662871] b44: eth0: powering down PHY May 25 19:22:24 Slejpner kernel: [ 3267.870455] ADDRCONF(NETDEV_UP): eth0: link is not ready May 25 19:22:28 Slejpner kernel: [ 3271.219899] b44: eth0: Link is up at 100 Mbps, full duplex. May 25 19:22:28 Slejpner kernel: [ 3271.219909] b44: eth0: Flow control is off for TX and off for RX. May 25 19:22:28 Slejpner kernel: [ 3271.220250] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready May 25 19:22:53 Slejpner pppd[4761]: PPP session is 3757 May 25 19:22:53 Slejpner pppd[4761]: Using interface ppp0 May 25 19:22:53 Slejpner pppd[4761]: Connect: ppp0 -- eth0 May 25 19:22:53 Slejpner pppd[4761]: CHAP authentication succeeded May 25 19:22:53 Slejpner pppd[4761]: CHAP authentication succeeded May 25 19:22:53 Slejpner pppd[4761]: peer from calling number 00:90:1A:A0:F4:5A authorized May 25 19:22:54 Slejpner pppd[4761]: local IP address 78.54.111.171 May 25 19:22:54 Slejpner pppd[4761]: remote IP address 213.191.76.38 May 25 19:22:54 Slejpner pppd[4761]: primary DNS address 213.191.74.19 May 25 19:22:54 Slejpner pppd[4761]: secondary DNS address 62.109.123.197 Other stuff that might help: a...@slejpner:~$ uname -a Linux Slejpner 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux a...@slejpner:~$ a...@slejpner:~$ ls -l /lib/libc.so.6 lrwxrwxrwx 1 root root 11 16. Mai 00:36 /lib/libc.so.6 - libc-2.7.so a...@slejpner:~$ a...@slejpner:~$ dpkg -s libc6 | grep ^Version Version: 2.7-18 a...@slejpner:~$ reportbug -q --template -T none -s none -S normal -b --list-cc none -q base Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Arne mydebian.b...@web.de' as your from address. Getting status for base... Will send report to Debian (per lsb_release). Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Arne mydebian.b...@web.de To: Debian Bug Tracking System sub...@bugs.debian.org Subject: none X-Debbugs-Cc: mydebian.b...@web.de, none Package: base Severity: normal -- System Information: Debian Release: 5.0 APT prefers proposed-updates APT policy: (99, 'proposed-updates'), (99, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash The system is running on a hp nx7400 laptop with 1 GB ram and 250 GB Samsung Harddisk. No problems what soever while using Etch. Good Luck thank you very much ! __ Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele ausländische Netze zum gleichen Preis! https://produkte.web.de/webde_sms/sms signature.asc Description: This is a digitally signed message part.
Bug#509733: Also broken on Intel G45 integrated graphics
As far as I know I am using the latest version of xserver-xorg-core available anywhere in Debian: where can I get one that *does* work? :; dpkg -l xserver-xorg-core Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii xserver-xorg-c 2:1.6.1.901-2 Xorg X server - core server :; X -version This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the xorg product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.6.1.901 (1.6.2 RC 1) Release Date: 2009-5-8 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-1-vserver-amd64 x86_64 Debian Current Operating System: Linux lsip 2.6.26-2-xen-amd64 #1 SMP Wed May 13 18:43:45 UTC 2009 x86_64 Build Date: 14 May 2009 04:42:17PM xorg-server 2:1.6.1.901-2 (bui...@excelsior.roeckx.be) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
