Siduction Forum

Siduction Forum => Siduction News => Topic started by: devil on 2012/12/11, 09:53:09

Title: Kernel 3.7 available
Post by: devil on 2012/12/11, 09:53:09: Kernel 3.7 has arrived in a stable version. As it has many changes, we would like to have it tested on as much hardware as possible. So for now we have it in our siduction experimental repository. If you want to test, just add the repo to your sources and dist-upgrade after a apt-get update. Please add your feedback here. Thanks.

greetz
devil
Title: RE: Kernel 3.7 available
Post by: vilde on 2012/12/11, 10:30:31: Added experimental, apt-get update, apt-get dist-upgrade and there is nothing to upgrade?
Title: RE: Kernel 3.7 available
Post by: towo on 2012/12/11, 11:16:05: Code: [Select]
towo@Druck-Buero:~$ LANG=C apt-cache policy linux-image-siduction-amd64 linux-image-siduction-amd64: Installed: 3.6-14 Candidate: 3.7-1 Version table: 3.7-1 0 500 http://packages.siduction.org/experimental/ unstable/main amd64 Packages 3.6-17 0 500 http://packages.siduction.org/base/ unstable/main amd64 Packages *** 3.6-14 0 100 /var/lib/dpkg/status
Maybe not on our mirrors yet.
Title: RE: Kernel 3.7 available
Post by: devil on 2012/12/11, 11:21:03: Maybe your mirror does not have the packages yet. Works for spline mirror here.

greetz
devil
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/11, 11:36:45: This is odd -- my netbook can see the package, but apt doesn't want to upgrade it.

Code: [Select]
root@tosh205:/etc/apt/sources.list.d# apt-cache policy linux-image-siduction-686 linux-image-siduction-686: Installed: 3.6-17 Candidate: 3.6-17 Version table: 3.7-1 0 100 http://packages.siduction.org/experimental/ unstable/main i386 Packages *** 3.6-17 0 500 http://packages.siduction.org/base/ unstable/main i386 Packages 100 /var/lib/dpkg/status

Perhaps it is waiting for the header package or something?
Title: RE: Kernel 3.7 available
Post by: towo on 2012/12/11, 11:45:23: The pinning is to low for our experimental.
Title: Kernel 3.7 available
Post by: vilde on 2012/12/11, 12:05:13: Code: [Select]
vilde@T400siductionbox64:~$ LANG=C apt-cache policy linux-image-siduction-amd64 linux-image-siduction-amd64: Installed: 3.6-17 Candidate: 3.6-17 Version table: 3.7-1 0 100 http://ftp.spline.de/pub/siduction/experimental/ unstable/main amd64 Packages *** 3.6-17 0 500 http://ftp.spline.de/pub/siduction/base/ unstable/main amd64 Packages 100 /var/lib/dpkg/status vilde@T400siductionbox64:~$ su Lösenord: root@T400siductionbox64:/home/vilde# apt-get dist-upgrade -d Läser paketlistor... Färdig Bygger beroendeträd Läser tillståndsinformation... Färdig Beräknar uppgradering... Färdig 0 att uppgradera, 0 att nyinstallera, 0 att ta bort och 0 att inte uppgradera.Sorry for the Swedish but I think you understand anyway.
Quote
The pinning is to low for our experimental.
Does this mean that apt doesn't rank experimental packages enough high or something like that?
Title: Kernel 3.7 available
Post by: dibl on 2012/12/11, 12:44:06: If you want to leave the default source priorities alone, you can simply do this:

Code: [Select]
root@tosh205:/home/don# apt-get install linux-image-3.7-0.towo-siduction-686

then reboot and boot the new kernel

then

Code: [Select]
root@tosh205:/home/don# apt-get install linux-headers-`uname -r`

and you are good to go with 3.7.

Code: [Select]
don@tosh205:~$ uname -a Linux tosh205 3.7-0.towo-siduction-686 #1 SMP PREEMPT Tue Dec 11 07:53:04 UTC 2012 i686 GNU/Linux
Title: Kernel 3.7 available
Post by: vilde on 2012/12/11, 13:28:43: Done :)
Code: [Select]
System: Host: T400siductionbox64 Kernel: 3.7-0.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2) Desktop: Xfce 4.10.0 (Gtk 2.24.10) Distro: siduction 12.2.0 Riders on the Storm - xfce - (201212092126) Machine: System: LENOVO product: 6474BB4 version: ThinkPad T400 Mobo: LENOVO model: 6474BB4 Bios: LENOVO version: 7UET49WW (1.19 ) date: 10/17/2008 CPU: Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9575.98 Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz Graphics: Card: Intel Mobile 4 Series Chipset Integrated Graphics Controller bus-ID: 00:02.0 X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1440x900@60.3hz GLX Renderer: Mesa DRI Mobile Intel GM45 Express Chipset GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes Network: Card-1: Intel Ultimate N WiFi Link 5300 driver: iwlwifi ver: in-tree: bus-ID: 03:00.0 IF: wlan0 state: up mac: 00:16:ea:e6:27:3a Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 2.1.4-k port: 1840 bus-ID: 00:19.0 IF: eth0 state: down mac: 00:1c:25:99:37:a2 Drives: HDD Total Size: 64.0GB (15.5% used) 1: model: Corsair_CSSD Info: Processes: 141 Uptime: 2 min Memory: 293.9/3856.3MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20 So far so good, I have not noticed any difference from before, that's probably a good sign
Title: RE: Kernel 3.7 available
Post by: devil on 2012/12/11, 13:54:10: apt-get install works in any case.
If you want to use virtualbox with 3.7, you need to go to Oracle and fetch the
Code: [Select]
virtualbox-4.2_4.2.4-81684~Debian~wheezypackage. Delete everything installed through apt and then install the .deb. Works fine, incl. extpack (at least for amd64).

greetz
devil
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/11, 15:44:20: Here is my report for 5 siduction systems:

These three have no problems (audio, video, and networking):

Code: [Select]
System: Host: tosh205 Kernel: 3.7-0.towo-siduction-686 i686 (32 bit, gcc: 4.7.2) Desktop: LXDE (Openbox 3.5.0) Distro: siduction 12.1 Desperado - lxde - (201205212227) Machine: System: TOSHIBA product: TOSHIBA NB205 version: PLL20U-00201D Mobo: TOSHIBA model: KAVAA version: 1.00 Bios: TOSHIBA version: V1.90 date: 01/15/2010 CPU: Single core Intel Atom CPU N280 (-HT-) cache: 512 KB flags: (nx sse sse2 sse3 ssse3) bmips: 3325.23 Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller bus-ID: 00:02.0 X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.0hz GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 8.0.5 Direct Rendering: Yes Network: Card-1: Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 03:00.0 IF: wlan0 state: up mac: 00:23:08:96:77:a1 Card-2: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 ver: 2.3LK-NAPI port: 2000 bus-ID: 04:00.0 IF: eth0 state: down mac: 00:23:5a:fa:a0:32 Drives: HDD Total Size: 40.0GB (0.9% used) 1: model: OCZ Info: Processes: 123 Uptime: 5 min Memory: 311.6/2016.7MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

Code: [Select]
System: Host: siductionbox Kernel: 3.7-0.towo-siduction-686 i686 (32 bit, gcc: 4.7.2) Desktop: LXDE (Openbox 3.5.0) Distro: siduction 12.2.0~rc1 Riders on the Storm - lxde - (201211192043) Machine: System: Gateway product: E-2100 version: 4000812 Mobo: Intel model: D845GVSR version: AAC44832-104 Bios: Intel version: SR84510A.15A.0013.P03.0308040832 date: 08/04/2003 CPU: Single core Intel Celeron CPU (-UP-) cache: 128 KB flags: (sse sse2) bmips: 4999.22 clocked at 2499.614 MHz Graphics: Card: Intel 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device bus-ID: 00:02.0 X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1600x1200@75.0hz GLX Renderer: Mesa DRI Intel 845G x86/MMX/SSE2 GLX Version: 1.3 Mesa 8.0.5 Direct Rendering: Yes Network: Card-1: Intel 82801DB PRO/100 VE (LOM) Ethernet Controller driver: e100 ver: 3.5.24-k2-NAPI port: df00 bus-ID: 01:08.0 IF: eth0 state: down mac: 00:0c:f1:73:7f:ac Card-2: Belkin F7D2102 802.11n N300 Micro Wireless Adapter v3000 [Realtek RTL8192CU] driver: rtl8192cu usb-ID: 001-002 IF: wlan0 state: up mac: 08:86:3b:02:d6:13 Drives: HDD Total Size: 160.0GB (0.2% used) 1: model: WDC_WD1600BB Info: Processes: 119 Uptime: 6 min Memory: 67.0/493.5MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

Code: [Select]
System: Host: emsputer Kernel: 3.7-0.towo-siduction-686-pae i686 (32 bit, gcc: 4.7.2) Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: siduction 12.1.1 Desperado Reloaded - kde - (201206241910) Machine: Mobo: Intel model: D975XBX version: AAD27094-305 serial: BQBX63100032 Bios: Intel version: BX97510J.86A.1487.2007.0902.1724 date: 09/02/2007 CPU: Single core Intel Pentium D CPU (-UP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 vmx) bmips: 7139.85 clocked at 3400.00 MHz Graphics: Card: Advanced Micro Devices [AMD] nee ATI R430 [Radeon X800 (PCIE)] bus-ID: 02:00.0 X.org: 1.12.4 drivers: fbdev,vesa tty size: 154x39 Advanced Data: N/A for root Network: Card-1: Intel 82573L Gigabit Ethernet Controller driver: e1000e ver: 2.1.4-k port: 2000 bus-ID: 05:00.0 IF: eth0 state: down mac: 00:16:76:b1:66:ea Card-2: Atheros TP-Link TL-WN821N v3 802.11n [Atheros AR7010+AR9287] driver: ath9k_htc usb-ID: 001-002 IF: wlan3 state: up mac: 90:f6:52:0a:c0:16 Drives: HDD Total Size: 1000.2GB (7.7% used) 1: model: WDC_WD1001FALS Info: Processes: 174 Uptime: 1 min Memory: 322.6/6079.2MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

I have two systems with Nvidia graphics, and they have two different problems.

This one boots 3.7 and the boot messages look OK, but the video driver is not loaded, so after it tries and fails to run X it gives me a console login:

Code: [Select]
System: Host: imerabox Kernel: 3.6-10.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2) Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: aptosid 2011-02 Ἡμέρα - kde-lite - (201107131633) Machine: Mobo: ASUSTeK model: P6X58D-E version: Rev 1.xx Bios: American Megatrends version: 0602 date: 03/24/2011 CPU: Quad core Intel Core i7 CPU 950 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 33735.8 Clock Speeds: 1: 4216.975 MHz 2: 4216.975 MHz 3: 4216.975 MHz 4: 4216.975 MHz 5: 4216.975 MHz 6: 4216.975 MHz 7: 4216.975 MHz 8: 4216.975 MHz Graphics: Card: NVIDIA GF100 [GeForce GTX 480] bus-ID: 05:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1920x1200@59.9hz GLX Renderer: GeForce GTX 480/PCIe/SSE2 GLX Version: 4.2.0 NVIDIA 304.64 Direct Rendering: Yes Network: Card: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2 ver: 1.30 port: d800 bus-ID: 06:00.0 IF: eth0 state: up speed: 100 Mbps duplex: full mac: 20:cf:30:5c:41:1d Drives: HDD Total Size: 2136.5GB (3.3% used) 1: model: OCZ 2: model: OCZ 3: model: KINGSTON_SS100S2 4: model: WDC_WD1002FAEX 5: model: WDC_WD1002FAEX Info: Processes: 324 Uptime: 4 min Memory: 1280.9/5965.7MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

I reinstalled nvidia-glx but it was already the current package. I did not capture the xorg.0.log file like I should have -- if you need to see it I'll boot it again and get the log file.

This one kernel panics on 3.7, image below:

Code: [Select]
System: Host: delle6500 Kernel: 3.6-10.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2) Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: siduction 12.1-RC1 Desperado - kde - (201205152133) Machine: System: Dell product: Latitude E6500 Mobo: Dell model: 0PP476 Bios: Dell version: A14 date: 07/31/2009 CPU: Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9575.8 Clock Speeds: 1: 2401.00 MHz 2: 2401.00 MHz Graphics: Card: NVIDIA G98M [Quadro NVS 160M] bus-ID: 01:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1920x1200@60.0hz GLX Renderer: Quadro NVS 160M/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 304.64 Direct Rendering: Yes Network: Card-1: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge bus-ID: 0c:00.0 IF: wlan0 state: up mac: 00:23:4e:ab:86:7a Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 2.0.0-k port: efe0 bus-ID: 00:19.0 IF: eth1 state: down mac: 00:21:70:d4:d3:04 Drives: HDD Total Size: 120.0GB (46.2% used) 1: model: OCZ_VERTEX Info: Processes: 182 Uptime: 13 min Memory: 1120.7/3948.0MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

(http://img145.imageshack.us/img145/166/l1070518.jpg) (http://imageshack.us/photo/my-images/145/l1070518.jpg/)

I tried it 3 or 4 times, all with this result.
Title: RE: Kernel 3.7 available
Post by: towo on 2012/12/11, 15:48:50: Your nvidia-computers needs driver 310.19 from experimental or the fixed one from our fixes-repo.
For the panic i have no clue at the moment.
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/11, 15:57:55: Thank you towo.

But, on the Nvidia driver, it looks like I don't understand something about the repo:

Code: [Select]
don@imerabox:/etc/apt/sources.list.d$ cat siduction.list | grep fixes deb http://packages.siduction.org/fixes unstable main #deb-src http://packages.siduction.org/fixes unstable main don@imerabox:/etc/apt/sources.list.d$ apt-cache policy nvidia-glx nvidia-glx: Installed: 304.64-2 Candidate: 304.64-2 Version table: *** 304.64-2 0 500 http://ftp.us.debian.org/debian/ unstable/non-free amd64 Packages 500 http://http.debian.net/debian/ unstable/non-free amd64 Packages 100 /var/lib/dpkg/status

What did I miss?
Title: RE: Kernel 3.7 available
Post by: towo on 2012/12/11, 16:01:29: Code: [Select]
root@Druck-Buero:/home/towo/test# apt-cache policy nvidia-kernel-dkms nvidia-glx nvidia-kernel-dkms: Installiert: 310.19-0+exp1 Installationskandidat: 310.19-0+exp1 Versionstabelle: *** 310.19-0+exp1 0 1 http://http.debian.net/debian/ experimental/non-free amd64 Packages 1 http://ftp.de.debian.org/debian/ experimental/non-free amd64 Packages 100 /var/lib/dpkg/status 304.64-2.1 0 500 http://packages.siduction.org/fixes/ unstable/non-free amd64 Packages 304.64-2 0 500 http://http.debian.net/debian/ sid/non-free amd64 Packages 304.48-1 0 500 http://ftp.de.debian.org/debian/ testing/non-free amd64 Packages 304.37-0 0 500 http://packages.siduction.org/user/ unstable/non-free amd64 Packages nvidia-glx: Installiert: 310.19-0+exp1 Installationskandidat: 310.19-0+exp1 Versionstabelle: *** 310.19-0+exp1 0 1 http://http.debian.net/debian/ experimental/non-free amd64 Packages 1 http://ftp.de.debian.org/debian/ experimental/non-free amd64 Packages 100 /var/lib/dpkg/status 304.64-2.1 0 500 http://packages.siduction.org/fixes/ unstable/non-free amd64 Packages 304.64-2 0 500 http://http.debian.net/debian/ sid/non-free amd64 Packages 304.48-1 0 500 http://ftp.de.debian.org/debian/ testing/non-free amd64 Packages 304.37-0 0 500 http://packages.siduction.org/user/ unstable/non-free amd64 Packages
Nvidia is non-free, you know? ;)
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/11, 16:09:00: puh -- I had commented out debian-experimental for some reason ....

Yes, "non-free" and sometimes the price is also high in brain cells!

:)

Vielen Dank!
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/11, 16:21:05: OK the 310-19 Nvidia driver fixed the Asus system -- audio, video, and networking all look fine now.

But I noticed the message that the 310-19 driver is not recommended for the old Quadro GPUs, such as the one in the Dell. So I guess the kernel panic is not related to the video system at all.
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/12, 00:28:48: I fixed the Dell E6500 kernel panic issue, by removing the kernel and reinstalling it. It must have been a failure of some kind during the first installation.

However, neither Nvidia driver would install on 3.7. Actually, 310-19 would install but would not drive the Quadro correctly, so I had to nuke the Nvidia drivers and install the nouveau driver. It looks fine, so no complaints.

Code: [Select]
System: Host: delle6500 Kernel: 3.7-0.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2) Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: siduction 12.1-RC1 Desperado - kde - (201205152133) Machine: System: Dell product: Latitude E6500 Mobo: Dell model: 0PP476 Bios: Dell version: A14 date: 07/31/2009 CPU: Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9575.98 Clock Speeds: 1: 2401.00 MHz 2: 2393.995 MHz Graphics: Card: NVIDIA G98M [Quadro NVS 160M] bus-ID: 01:00.0 X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz GLX Renderer: Gallium 0.4 on NV98 GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes Network: Card-1: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge bus-ID: 0c:00.0 IF: wlan0 state: up mac: 00:23:4e:ab:86:7a Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 2.1.4-k port: efe0 bus-ID: 00:19.0 IF: eth1 state: down mac: 00:21:70:d4:d3:04 Drives: HDD Total Size: 120.0GB (46.0% used) 1: model: OCZ_VERTEX Info: Processes: 176 Uptime: 11 min Memory: 891.8/3948.4MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20
Title: RE: Kernel 3.7 available
Post by: towo on 2012/12/12, 07:59:06: Dibl, in our fixes-repo i have put a fixed 304.62 driver, which is compatible with kernel 3.7.
Title: RE: Kernel 3.7 available
Post by: dibl on 2012/12/12, 12:57:40: Thank you towo.

I used your new Nvidia driver package to set up with 3.7 on this old laptop:

Code: [Select]
System: Host: latitude-D620 Kernel: 3.7-0.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2) Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: siduction 12.1.1 Desperado Reloaded - kde - (201206241901) Machine: System: Dell product: Latitude D620 Mobo: Dell model: 0KX350 Bios: Dell version: A10 date: 05/16/2008 CPU: Dual core Intel Core2 CPU T7200 (-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7989.58 Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz Graphics: Card: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] bus-ID: 01:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1440x900@60.0hz GLX Renderer: GeForce Go 7300/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.64 Direct Rendering: Yes Network: Card-1: Broadcom NetXtreme BCM5752 Gigabit Ethernet PCI Express driver: tg3 ver: 3.125 bus-ID: 09:00.0 IF: eth0 state: down mac: 00:18:8b:d6:2c:8f Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945 ver: in-tree:s bus-ID: 0c:00.0 IF: wlan0 state: up mac: 00:1b:77:37:e7:b5 Drives: HDD Total Size: 100.0GB (5.9% used) 1: model: Hitachi_HTS72101 Info: Processes: 165 Uptime: 1 min Memory: 745.2/3267.1MB Runlevel: 5 Gcc sys: 4.7.2 Client: Shell inxi: 1.8.20

Video, audio, and networking all looks good.
Title: RE: Kernel 3.7 available
Post by: vilde on 2012/12/20, 20:05:53: I´m not sure f this have to do with the kernel but after d-u on my media-box among others upgrading the kernel from 3.6.9 to 3.7.1 something hapen to my hdmi out sound, I had to reconfigure my .asoundrc to make it work again. I wrote about it here: http://forum.siduction.org/index.php?msg=26490#26490