Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
SS4000E Kernel v3.4 Config
217 views
Skip to first unread message
Chris Wilkinson
Jul 31, 2012, 12:10:03 PM7/31/12
to
Does anyone have a .config for the kernel v3.4.0 menuconfig they could post?
The kernel builds Ok with tweaked Arnaud's patches
(http://lists.debian.org/debian-arm/2012/07/msg00167.html) for the LEDs but
the ss4000e doesn't boot using the built zImage and ss4000e initrd.gz.
I may be missing some important setting.
Mine is here
http://pastebin.com/0LCkY06F
CJW
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/001801cd6f36$3cfb1f20$b6f15d60$@net
The kernel builds Ok with tweaked Arnaud's patches
(http://lists.debian.org/debian-arm/2012/07/msg00167.html) for the LEDs but
the ss4000e doesn't boot using the built zImage and ss4000e initrd.gz.
I may be missing some important setting.
Mine is here
http://pastebin.com/0LCkY06F
CJW
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/001801cd6f36$3cfb1f20$b6f15d60$@net
Arnaud Patard
Jul 31, 2012, 12:30:02 PM7/31/12
to
"Chris Wilkinson" <kin...@verizon.net> writes:
> Does anyone have a .config for the kernel v3.4.0 menuconfig they could post?
> The kernel builds Ok with tweaked Arnaud's patches
> (http://lists.debian.org/debian-arm/2012/07/msg00167.html) for the LEDs but
> the ss4000e doesn't boot using the built zImage and ss4000e initrd.gz.
>
> I may be missing some important setting.
>
> Mine is here
>
> http://pastebin.com/0LCkY06F
CONFIG_ARCH_VERSATILE=y
> Does anyone have a .config for the kernel v3.4.0 menuconfig they could post?
> The kernel builds Ok with tweaked Arnaud's patches
> (http://lists.debian.org/debian-arm/2012/07/msg00167.html) for the LEDs but
> the ss4000e doesn't boot using the built zImage and ss4000e initrd.gz.
>
> I may be missing some important setting.
>
> Mine is here
>
> http://pastebin.com/0LCkY06F
# CONFIG_ARCH_IOP32X is not set
your kernel is not correctly configured. Your configuration is only good
if you want to boot your system on Qemu. You need at least to configure
your kernel for the right SoC and machine.
If you don't know exactly what to set, I would advice to use debian's
configuration for iop32x systems and enable the drivers added by my
patches. You may also have to take care about machine number stuff too
(the archive of this mailing list has probably the infos about this).
Arnaud
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Jul 31, 2012, 4:10:02 PM7/31/12
to
That's good advice. Where could I get the configuration from?
Chris
Archive: http://lists.debian.org/004201cd6f57$f960a1f0$ec21e5d0$@net
Chris
Chris Wilkinson
Aug 2, 2012, 10:20:02 AM8/2/12
to
I built a kernel zImage which is of size 2.77MB. This is too big to fit in
the FLASH space allocated for it in EM7220 Redboot fis (2MB) so although d-i
runs OK it fails on the final step of making the system bootable. Fis errors
if I try to fis create zImage after the load for the same reason.
Can anyone suggest some tricks to shrink it a bit?
Here are the steps I followed, largely based on Arnaud's advice.
Based the config on the iop32x_defconfig in ./arch/arm/configs of the Linux
3.4 distribution. Then added Arnaud's patches
http://git.rtp-net.org/?p=ss4000e.git;a=tree for F751111 in the following
order
gpiolib_regs_show.patch
f75111.patch
add_f75111_pdata.patch
em7210_report_ac_status.patch
em7210_add_missing_leds.patch
f75111.patch fails with the following reject ./drivers/gpio/Kconfig.rej for
reasons unknown to me.
--- drivers/gpio/Kconfig 2012-05-29 00:48:29.000000000 +0200
+++ drivers/gpio/Kconfig 2012-05-29 00:53:01.915204251 +0200
@@ -558,4 +558,16 @@
Enable support for GPIO on intel MSIC controllers found in
intel MID devices
+config F75111
+ tristate "Fintec F75111 chip"
+ depends on I2C
+ depends on GPIOLIB
+ depends on LEDS_CLASS
+ help
+ Say yes here if you need support for the Fintec F75111 GPIO/LED
+ chip.
+
+ This driver can also be built as a module. If so, the module
+ will be called f75111.
+
Endif
The added (+) lines which were not patched were added manually to the end of
./drivers/gpio/Kconfig
The general procedure is here
http://briolidz.wordpress.com/2012/02/07/building-embedded-arm-systems-with-
crosstool-ng/ modified a bit for linux 3.4 and iop32x.
Define the arch, initial .config
$ make ARCH=arm iop32x_defconfig
Modify the arm iop32x one
$ make ARCH=arm menuconfig (or nconfig)
Use EABI
> Kernel Features > Use the ARM EABI to compile the kernel
Update .config with w83792, f751111 drivers
> Device Drivers
> LED Support > LED Class Support
> LED Support > LED Support for GPIO connected LEDs
> GPIO Support > Fintec 751111
> Device Drivers > Hardware Mon > Winbond w83792
Build using the crostool-ng toolset.
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- all
zImage is in ./arch/arm/boot
CJW
Archive: http://lists.debian.org/001c01cd70b8$e7431900$b5c94b00$@net
the FLASH space allocated for it in EM7220 Redboot fis (2MB) so although d-i
runs OK it fails on the final step of making the system bootable. Fis errors
if I try to fis create zImage after the load for the same reason.
Can anyone suggest some tricks to shrink it a bit?
Here are the steps I followed, largely based on Arnaud's advice.
Based the config on the iop32x_defconfig in ./arch/arm/configs of the Linux
3.4 distribution. Then added Arnaud's patches
http://git.rtp-net.org/?p=ss4000e.git;a=tree for F751111 in the following
order
gpiolib_regs_show.patch
f75111.patch
add_f75111_pdata.patch
em7210_report_ac_status.patch
em7210_add_missing_leds.patch
f75111.patch fails with the following reject ./drivers/gpio/Kconfig.rej for
reasons unknown to me.
--- drivers/gpio/Kconfig 2012-05-29 00:48:29.000000000 +0200
+++ drivers/gpio/Kconfig 2012-05-29 00:53:01.915204251 +0200
@@ -558,4 +558,16 @@
Enable support for GPIO on intel MSIC controllers found in
intel MID devices
+config F75111
+ tristate "Fintec F75111 chip"
+ depends on I2C
+ depends on GPIOLIB
+ depends on LEDS_CLASS
+ help
+ Say yes here if you need support for the Fintec F75111 GPIO/LED
+ chip.
+
+ This driver can also be built as a module. If so, the module
+ will be called f75111.
+
Endif
The added (+) lines which were not patched were added manually to the end of
./drivers/gpio/Kconfig
The general procedure is here
http://briolidz.wordpress.com/2012/02/07/building-embedded-arm-systems-with-
crosstool-ng/ modified a bit for linux 3.4 and iop32x.
Define the arch, initial .config
$ make ARCH=arm iop32x_defconfig
Modify the arm iop32x one
$ make ARCH=arm menuconfig (or nconfig)
Use EABI
> Kernel Features > Use the ARM EABI to compile the kernel
Update .config with w83792, f751111 drivers
> Device Drivers
> LED Support > LED Class Support
> LED Support > LED Support for GPIO connected LEDs
> GPIO Support > Fintec 751111
> Device Drivers > Hardware Mon > Winbond w83792
Build using the crostool-ng toolset.
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- all
zImage is in ./arch/arm/boot
CJW
Arnaud Patard
Aug 2, 2012, 10:40:01 AM8/2/12
to
"Chris Wilkinson" <kin...@verizon.net> writes:
> I built a kernel zImage which is of size 2.77MB. This is too big to fit in
> the FLASH space allocated for it in EM7220 Redboot fis (2MB) so although d-i
> runs OK it fails on the final step of making the system bootable. Fis errors
> if I try to fis create zImage after the load for the same reason.
>
> Can anyone suggest some tricks to shrink it a bit?
>
> Here are the steps I followed, largely based on Arnaud's advice.
>
> Based the config on the iop32x_defconfig in ./arch/arm/configs of the
> Linux
the defconfig would probably enable too many things. In the debian
> I built a kernel zImage which is of size 2.77MB. This is too big to fit in
> the FLASH space allocated for it in EM7220 Redboot fis (2MB) so although d-i
> runs OK it fails on the final step of making the system bootable. Fis errors
> if I try to fis create zImage after the load for the same reason.
>
> Can anyone suggest some tricks to shrink it a bit?
>
> Here are the steps I followed, largely based on Arnaud's advice.
>
> Based the config on the iop32x_defconfig in ./arch/arm/configs of the
> Linux
package, we're making sure that it's not more than 1441784B so it would
fit in 2MB. Look at your /boot if you already installed a debian kernel
before. Otherwise, download the deb from a mirror and extract its
content in a temporary directory and you'll get a boot/config-$VERSION.
Arnaud
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Aug 2, 2012, 9:20:02 PM8/2/12
to
Thanks again to Arnaud for suggesting that a smaller size zImage generating
menuconfig .config can be extracted in boot/config-3.2.0-3-iop32x of the deb
downloaded from
http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
_3.2.23-1_armel.deb
Indeed it does. This generates a zImage of 1.53MB which is good, <2MB.
However d-i fails to detect the network card on the EM7220 which I would
think is the same as the 7210.
And it's none of these listed by d-i, it's an on board Intel 82541PI
http://em7210.kwaak.net/cgi-bin/trac.cgi/wiki/HardwareDetails. There must be
another setting error since the iop32x_defconfig which created the too large
zImage detected the network.
I don't see this device in Device Drivers > Network Device Support of
menuconfig.
What to do?
d-i trace
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ [!] Detect network hardware ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³
³
³ No Ethernet card was detected. If you know the name of the driver
³
³ needed by your Ethernet card, you can select it from the list.
³
³
³
³ Driver needed by your Ethernet card:
³
³
³
³ no ethernet card
³
³ e1000: Intel(R) PRO/1000 Gigabit Ethernet
³
³ libphy
³
³ r8169: RealTek RTL-8169 Gigabit Ethernet
³
³ sis190: SiS 190 PCI Gigabit Ethernet
³
³ skge
³
³ tg3: Broadcom Tigon3 Gigabit Ethernet
³
³ none of the above
³
³
³
³ <Go Back>
³
³
³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
CJW
-----Original Message-----
From: Arnaud Patard (Rtp) [mailto:arnaud...@rtp-net.org]
Sent: Thursday, August 02, 2012 10:34 AM
To: Chris Wilkinson
Cc: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/004c01cd7115$67fdf180$37f9d480$@net
menuconfig .config can be extracted in boot/config-3.2.0-3-iop32x of the deb
downloaded from
http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
_3.2.23-1_armel.deb
Indeed it does. This generates a zImage of 1.53MB which is good, <2MB.
However d-i fails to detect the network card on the EM7220 which I would
think is the same as the 7210.
And it's none of these listed by d-i, it's an on board Intel 82541PI
http://em7210.kwaak.net/cgi-bin/trac.cgi/wiki/HardwareDetails. There must be
another setting error since the iop32x_defconfig which created the too large
zImage detected the network.
I don't see this device in Device Drivers > Network Device Support of
menuconfig.
What to do?
d-i trace
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ [!] Detect network hardware ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³
³
³ No Ethernet card was detected. If you know the name of the driver
³
³ needed by your Ethernet card, you can select it from the list.
³
³
³
³ Driver needed by your Ethernet card:
³
³
³
³ no ethernet card
³
³ e1000: Intel(R) PRO/1000 Gigabit Ethernet
³
³ libphy
³
³ r8169: RealTek RTL-8169 Gigabit Ethernet
³
³ sis190: SiS 190 PCI Gigabit Ethernet
³
³ skge
³
³ tg3: Broadcom Tigon3 Gigabit Ethernet
³
³ none of the above
³
³
³
³ <Go Back>
³
³
³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
CJW
-----Original Message-----
From: Arnaud Patard (Rtp) [mailto:arnaud...@rtp-net.org]
Sent: Thursday, August 02, 2012 10:34 AM
To: Chris Wilkinson
Cc: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Chris Wilkinson
Aug 7, 2012, 12:00:02 PM8/7/12
to
Continuing this quest to move my kernel to 3.4 so I can use Arnaud's LED
patches. This problem with v3.4 kernel failing to detect the network card
seems to be inherent in 3.4.
Latest attempt was to install using the daily-images
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/. This
results in kernel v2.6.32.5 which detects the n/w card fine, d-i completes
and it boots no problem. From the boot trace, the n/w driver used is
[ 13.750000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
Connection
CONFIG_E1000 is the flag in kernel .config.
I then copied config-2.6.32-5-iop32x that was put in /boot to configure the
3.4 kernel without any of Arnaud's patches. This builds fine and yields a
zImage of 1.5MB but also fails to detect the n/w card. It's also the same
using the _defconfig extracted from the deb at
http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
_3.2.23-1_armel.deb
I used the initrd.gz from the daily-images. I wonder if this is the problem?
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Thursday, August 02, 2012 9:15 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/001201cd74b5$105682a0$310387e0$@net
patches. This problem with v3.4 kernel failing to detect the network card
seems to be inherent in 3.4.
Latest attempt was to install using the daily-images
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/. This
results in kernel v2.6.32.5 which detects the n/w card fine, d-i completes
and it boots no problem. From the boot trace, the n/w driver used is
[ 13.750000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
Connection
CONFIG_E1000 is the flag in kernel .config.
I then copied config-2.6.32-5-iop32x that was put in /boot to configure the
3.4 kernel without any of Arnaud's patches. This builds fine and yields a
zImage of 1.5MB but also fails to detect the n/w card. It's also the same
using the _defconfig extracted from the deb at
http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
_3.2.23-1_armel.deb
I used the initrd.gz from the daily-images. I wonder if this is the problem?
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Thursday, August 02, 2012 9:15 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Arnaud Patard
Aug 7, 2012, 12:20:04 PM8/7/12
to
"Chris Wilkinson" <kin...@verizon.net> writes:
> Continuing this quest to move my kernel to 3.4 so I can use Arnaud's LED
> patches. This problem with v3.4 kernel failing to detect the network card
> seems to be inherent in 3.4.
>
> Latest attempt was to install using the daily-images
> http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/. This
> results in kernel v2.6.32.5 which detects the n/w card fine, d-i completes
> and it boots no problem. From the boot trace, the n/w driver used is
>
> [ 13.750000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
> Connection
>
> CONFIG_E1000 is the flag in kernel .config.
>
> I then copied config-2.6.32-5-iop32x that was put in /boot to configure the
> 3.4 kernel without any of Arnaud's patches. This builds fine and yields a
> zImage of 1.5MB but also fails to detect the n/w card. It's also the same
> using the _defconfig extracted from the deb at
> http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
> _3.2.23-1_armel.deb
>
> I used the initrd.gz from the daily-images. I wonder if this is the problem?
the network driver is in module so you need to find a way to load it
> Continuing this quest to move my kernel to 3.4 so I can use Arnaud's LED
> patches. This problem with v3.4 kernel failing to detect the network card
> seems to be inherent in 3.4.
>
> Latest attempt was to install using the daily-images
> http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/. This
> results in kernel v2.6.32.5 which detects the n/w card fine, d-i completes
> and it boots no problem. From the boot trace, the n/w driver used is
>
> [ 13.750000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
> Connection
>
> CONFIG_E1000 is the flag in kernel .config.
>
> I then copied config-2.6.32-5-iop32x that was put in /boot to configure the
> 3.4 kernel without any of Arnaud's patches. This builds fine and yields a
> zImage of 1.5MB but also fails to detect the n/w card. It's also the same
> using the _defconfig extracted from the deb at
> http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-3.2.0-3-iop32x
> _3.2.23-1_armel.deb
>
> I used the initrd.gz from the daily-images. I wonder if this is the problem?
while installing with d-i. Given that the zImage size is 1.5MB, maybe
you can try putting the ethernet driver built-in instead of module to
workaround that ?
Arnaud
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Aug 7, 2012, 1:50:03 PM8/7/12
to
I had tried that before but to be sure tried again.
Setting the e1000 driver to built-in instead of module and rebuild. 1.5M
still.
N/w card is detected this time but DHCP ip acquisition fails, so that's a
step forward I guess. I know DHCP is available from the n/w because 2.6.32
worked OK and other machines get it.
Continued to configure n/w manually with an IP, GW, DNS etc. This fails to
retrieve files from the Deb archive mirror, so the n/w is apparently not
functioning really.
CJW
-----Original Message-----
From: Arnaud Patard (Rtp) [mailto:arnaud...@rtp-net.org]
Sent: Tuesday, August 07, 2012 12:12 PM
To: Chris Wilkinson
Cc: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/001301cd74c4$41a72ee0$c4f58ca0$@net
Setting the e1000 driver to built-in instead of module and rebuild. 1.5M
still.
N/w card is detected this time but DHCP ip acquisition fails, so that's a
step forward I guess. I know DHCP is available from the n/w because 2.6.32
worked OK and other machines get it.
Continued to configure n/w manually with an IP, GW, DNS etc. This fails to
retrieve files from the Deb archive mirror, so the n/w is apparently not
functioning really.
CJW
-----Original Message-----
From: Arnaud Patard (Rtp) [mailto:arnaud...@rtp-net.org]
Sent: Tuesday, August 07, 2012 12:12 PM
To: Chris Wilkinson
Cc: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Chris Wilkinson
Aug 7, 2012, 5:30:01 PM8/7/12
to
The n/w card driver is set as module in the 2.6.32.5 /boot config that came
from the daily-images ss4000e.
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Tuesday, August 07, 2012 1:44 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/003601cd74e3$894b63f0$9be22bd0$@net
from the daily-images ss4000e.
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Tuesday, August 07, 2012 1:44 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Chris Wilkinson
Aug 9, 2012, 2:00:02 PM8/9/12
to
At the download installer components step, d-i halts with the error 'no
kernel modules found' which I think is fatal.
The same symptoms/error occurs for both 2.6.32.5 and 3.4 sources from
ftp.kernel.org.
I'm not sure where to go next? Any suggestions are hoped for.
Set n/w card e1000 driver to built-in
Patched zImage with the machine number patch (per Arnaud)
$ ( devio 'wl 0xe3a01c04,4' 'wl 0xe38110bc,4'; cat zImage ) >
zImage.ss4000e and then used zImage.ss4000e
## prepends 8 bytes machine code to set right machine number
zImage.ss4000e size is then 1492880 (for 3.4)
n/w card is detected
DHCP succeeds
No kernel modules error
Opened shell in d-i
$ uname -a
$ Linux new-host 3.4.0 #2 Tue Aug 7 12:49:41 EDT 2012 armv5tel GNU/Linux
Last few lines of /var/log/syslog are
Aug 9 17:59:33 main-menu[185]: INFO: Menu item 'netcfg' selected
Aug 9 17:59:35 kernel: [ 29.851890] e1000: eth0 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: RX/TX
Aug 9 17:59:38 udhcpc: Got IP 192.168.1.155 (using eth0) and routing
through 192.168.1.1
Aug 9 17:59:40 netcfg[769]: INFO: DHCP hostname: "new-host"
Aug 9 18:00:02 netcfg[769]: INFO: Detected eth0 as a hotpluggable device
Aug 9 18:00:02 main-menu[185]: (process:768): udhcpc (v1.17.1) started
Aug 9 18:00:02 main-menu[185]: (process:768): Sending discover...
Aug 9 18:00:02 main-menu[185]: (process:768): Sending discover...
Aug 9 18:00:02 main-menu[185]: (process:768): Sending select for
192.168.1.155...
Aug 9 18:00:02 main-menu[185]: (process:768): Lease of 192.168.1.155
obtained, lease time 86400
Aug 9 18:00:02 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:00:02 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:00:02 main-menu[185]: INFO: Menu item 'choose-mirror' selected
Aug 9 18:00:03 anna-install: Queueing udeb apt-mirror-setup for later
installation
Aug 9 18:00:07 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/oldstable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:07 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/stable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:09 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/squeeze/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:10 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/testing/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:12 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/wheezy/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:14 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/unstable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:15 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/sid/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:17 choose-mirror[833]: INFO: suite/codename set to:
stable/squeeze
Aug 9 18:00:17 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/squeeze/main/binary-armel/Release
-O - | grep ^Architecture:
Aug 9 18:00:18 anna-install: Queueing udeb squeeze-support for later
installation
Aug 9 18:00:18 main-menu[185]: (process:826): wget: server returned error:
HTTP/1.1 404 Not Found
Aug 9 18:00:18 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:00:18 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:00:18 main-menu[185]: INFO: Menu item 'download-installer'
selected
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: WARNING: multiple signatures detected. Only
the first will be checked.
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: Signature made Sat May 12 12:08:13 2012 UTC
using RSA key ID 473041FA
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: Good signature from "Debian Archive Automatic
Signing Key (6.0/squeeze) <ftpm...@debian.org>"
Aug 9 18:00:20 net-retriever:
Aug 9 18:00:23 anna[887]: WARNING **: no packages matching running kernel
3.4.0 in archive
Aug 9 18:30:25 main-menu[185]: INFO: Menu item 'download-installer'
succeeded but requested to be left unconfigured.
Aug 9 18:30:25 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:30:25 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:30:36 main-menu[185]: INFO: Menu item 'di-utils-shell' selected
~ #
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Tuesday, August 07, 2012 1:44 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/002401cd7657$631befe0$2953cfa0$@net
kernel modules found' which I think is fatal.
The same symptoms/error occurs for both 2.6.32.5 and 3.4 sources from
ftp.kernel.org.
I'm not sure where to go next? Any suggestions are hoped for.
Set n/w card e1000 driver to built-in
Patched zImage with the machine number patch (per Arnaud)
$ ( devio 'wl 0xe3a01c04,4' 'wl 0xe38110bc,4'; cat zImage ) >
zImage.ss4000e and then used zImage.ss4000e
## prepends 8 bytes machine code to set right machine number
zImage.ss4000e size is then 1492880 (for 3.4)
n/w card is detected
DHCP succeeds
No kernel modules error
Opened shell in d-i
$ uname -a
$ Linux new-host 3.4.0 #2 Tue Aug 7 12:49:41 EDT 2012 armv5tel GNU/Linux
Last few lines of /var/log/syslog are
Aug 9 17:59:33 main-menu[185]: INFO: Menu item 'netcfg' selected
Aug 9 17:59:35 kernel: [ 29.851890] e1000: eth0 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: RX/TX
Aug 9 17:59:38 udhcpc: Got IP 192.168.1.155 (using eth0) and routing
through 192.168.1.1
Aug 9 17:59:40 netcfg[769]: INFO: DHCP hostname: "new-host"
Aug 9 18:00:02 netcfg[769]: INFO: Detected eth0 as a hotpluggable device
Aug 9 18:00:02 main-menu[185]: (process:768): udhcpc (v1.17.1) started
Aug 9 18:00:02 main-menu[185]: (process:768): Sending discover...
Aug 9 18:00:02 main-menu[185]: (process:768): Sending discover...
Aug 9 18:00:02 main-menu[185]: (process:768): Sending select for
192.168.1.155...
Aug 9 18:00:02 main-menu[185]: (process:768): Lease of 192.168.1.155
obtained, lease time 86400
Aug 9 18:00:02 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:00:02 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:00:02 main-menu[185]: INFO: Menu item 'choose-mirror' selected
Aug 9 18:00:03 anna-install: Queueing udeb apt-mirror-setup for later
installation
Aug 9 18:00:07 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/oldstable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:07 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/stable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:09 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/squeeze/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:10 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/testing/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:12 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/wheezy/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:14 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/unstable/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:15 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/sid/Release -O - | grep -E
'^(Suite|Codename):'
Aug 9 18:00:17 choose-mirror[833]: INFO: suite/codename set to:
stable/squeeze
Aug 9 18:00:17 choose-mirror[833]: DEBUG: command: wget -q
http://ftp.us.debian.org/debian//dists/squeeze/main/binary-armel/Release
-O - | grep ^Architecture:
Aug 9 18:00:18 anna-install: Queueing udeb squeeze-support for later
installation
Aug 9 18:00:18 main-menu[185]: (process:826): wget: server returned error:
HTTP/1.1 404 Not Found
Aug 9 18:00:18 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:00:18 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:00:18 main-menu[185]: INFO: Menu item 'download-installer'
selected
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: WARNING: multiple signatures detected. Only
the first will be checked.
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: Signature made Sat May 12 12:08:13 2012 UTC
using RSA key ID 473041FA
Aug 9 18:00:20 net-retriever: gpgv:
Aug 9 18:00:20 net-retriever: Good signature from "Debian Archive Automatic
Signing Key (6.0/squeeze) <ftpm...@debian.org>"
Aug 9 18:00:20 net-retriever:
Aug 9 18:00:23 anna[887]: WARNING **: no packages matching running kernel
3.4.0 in archive
Aug 9 18:30:25 main-menu[185]: INFO: Menu item 'download-installer'
succeeded but requested to be left unconfigured.
Aug 9 18:30:25 main-menu[185]: DEBUG: resolver (libc6-udeb): package
doesn't exist (ignored)
Aug 9 18:30:25 main-menu[185]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug 9 18:30:36 main-menu[185]: INFO: Menu item 'di-utils-shell' selected
~ #
CJW
-----Original Message-----
From: Chris Wilkinson [mailto:kin...@verizon.net]
Sent: Tuesday, August 07, 2012 1:44 PM
To: 'Arnaud Patard (Rtp)'
Cc: debia...@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config
Chris Wilkinson
Aug 11, 2012, 12:50:02 PM8/11/12
to
For my experiments with building a new 2.5.32.5 kernel for the ss4000e I've
been using the initrd.gz from the latest ss4000e build at
http://d-i.debian.org/daily-images/armel/. I now think that initrd needs to
be rebuilt specifically for each kernel version. After getting to the point
in d-I where the 'no kernel modules found' error occurs, I go back and open
a d-I shell and see that the modules are at /lib/modules/2.6.32-5-iop32x/...
and this same path is of course in the initrd when I extract the initrd
files to a temporary directory with cpio. The version number of the kernel I
built (shell uname -a) is 2.6.32.5 so it's not surprising that d-I fails to
load any modules. Even adding -iop32x to the kernel version string in
menuconfig can't fix this (-5 not .5).
Does this seem like a correct conclusion that initrd must be rebuilt for
each kernel version?
This would also explain why the n/w card wasn't found if the e1000 driver is
set as a module but was found if set as built-in.
I guess there must be a build script for initrd.gz and zImage that are at
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/ which
I could use? But I failed to find it.
Archive: http://lists.debian.org/000001cd77e1$0ffedbc0$2ffc9340$@net
been using the initrd.gz from the latest ss4000e build at
http://d-i.debian.org/daily-images/armel/. I now think that initrd needs to
be rebuilt specifically for each kernel version. After getting to the point
in d-I where the 'no kernel modules found' error occurs, I go back and open
a d-I shell and see that the modules are at /lib/modules/2.6.32-5-iop32x/...
and this same path is of course in the initrd when I extract the initrd
files to a temporary directory with cpio. The version number of the kernel I
built (shell uname -a) is 2.6.32.5 so it's not surprising that d-I fails to
load any modules. Even adding -iop32x to the kernel version string in
menuconfig can't fix this (-5 not .5).
Does this seem like a correct conclusion that initrd must be rebuilt for
each kernel version?
This would also explain why the n/w card wasn't found if the e1000 driver is
set as a module but was found if set as built-in.
I guess there must be a build script for initrd.gz and zImage that are at
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/ which
I could use? But I failed to find it.
JF Straeten
Aug 11, 2012, 2:10:02 PM8/11/12
to
Chris,
On Sat, Aug 11, 2012 at 12:47:56PM -0400, Chris Wilkinson wrote:
[...]
> Does this seem like a correct conclusion that initrd must be rebuilt
> for each kernel version?
(In theory, if the modules are exactly the same and the changes to the
config are small, perhaps can one skip rebuilding initrd, but even in
this case, I'm not sure...)
Hih,
--
JFS.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Aug 12, 2012, 4:40:01 PM8/12/12
to
Unfortunately this doesn't appear so since the kernel version number is
embedded in paths within the initrd archive. If this doesn't match *exactly*
the kernel version, modules are not found.
Did you find a method to create an initrd based on the kernel version?
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Saturday, August 11, 2012 2:03 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/002301cd78ca$5e90d790$1bb286b0$@net
embedded in paths within the initrd archive. If this doesn't match *exactly*
the kernel version, modules are not found.
Did you find a method to create an initrd based on the kernel version?
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Saturday, August 11, 2012 2:03 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
JF Straeten
Aug 12, 2012, 5:50:02 PM8/12/12
to
Re,
On Sun, Aug 12, 2012 at 04:38:02PM -0400, Chris Wilkinson wrote:
> Unfortunately this doesn't appear so since the kernel version number
> is embedded in paths within the initrd archive. If this doesn't
> match *exactly* the kernel version, modules are not found.
> Did you find a method to create an initrd based on the kernel
> version?
update-initramfs -u
should do the trick...
Hih,
--
JFS.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Aug 15, 2012, 1:20:02 PM8/15/12
to
These tools seem to generate an initramfs for the host (AMD-64) system. I
want to build one for the ss4000e ARM target. Is that possible?
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Sunday, August 12, 2012 5:40 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/001001cd7b09$48589760$d909c620$@net
want to build one for the ss4000e ARM target. Is that possible?
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Sunday, August 12, 2012 5:40 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
JF Straeten
Aug 15, 2012, 2:30:02 PM8/15/12
to
Re,
On Wed, Aug 15, 2012 at 01:13:25PM -0400, Chris Wilkinson wrote:
> These tools seem to generate an initramfs for the host (AMD-64)
> system. I want to build one for the ss4000e ARM target. Is that
> possible?
(Not sure.)
Hih,
--
JFS.
--
To UNSUBSCRIBE, email to debian-ar...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Chris Wilkinson
Aug 17, 2012, 12:30:02 PM8/17/12
to
Do you think of this approach would work?
1. Load/boot ss4000e with the daily images kernel=v2.6.32-5
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/
It boots/runs 2.6.32-5
2. Cross-build new 3.4 kernel
3. Save modules and compress
$ export INSTALL_MOD_PATH=../modules-3.4 #make/put modules in
../modules-3.4
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- modules_install
$ cd ..
$ tar -zcvf modules-3.4.tar.gz modules-3.4 #compress
4. Fix zImage with Arnaud's devio trick to fix machine ID
5. Copy .config, System.map, zImage-3.4.0-iop32x, modules-3.4.tar.gz to tftp
server to upload them to ss4000e
6. Download these to a ss4000e working dir with tftp (needed to install
tftp)
7. Copy and rename downloaded to /boot per list below
8. Decompress modules-3.4.tar.gz. Copy the lib directory therein to /lib
9. Build initramfs in /boot
mkinitramfs -o initrd.img-3.4.0-iop32x 3.4.0
root@new-host:/boot# ls -l
total 10364
-rw-r--r-- 1 root root 81828 May 6 21:35 config-2.6.32-5-iop32x
-rw-r--r-- 1 root root 102426 Aug 17 10:08 config-3.4.0
lrwxrwxrwx 1 root root 26 Aug 16 17:34 initrd.img ->
initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2759115 Aug 16 17:59 initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2840619 Aug 17 10:09 initrd.img-3.4.0-iop32x
-rw-r--r-- 1 root root 945808 May 6 21:35 System.map-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1127522 Aug 17 09:32 System.map-3.4.0-iop32x
lrwxrwxrwx 1 root root 23 Aug 16 17:34 vmlinuz ->
vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1257376 May 6 21:34 vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1450536 Aug 17 09:33 zImage-3.4.0-iop32x
All the 3.4.0 files are in /boot but they are not yet linked. The ss4000e
will still boot as 2.6.32-5
10. Remake the 2 links so that initrd.img points to initrd-3.4.0-iop32x and
vmlinuz points to zImage-3.4.0-iop32x
11. Run flash-kernel to save
is initrd.img-3.4.0-iop32x too big?
12. Reboot and it should boot into 3.4 kernel??
I didn't actually take the last 3 steps. I'm not sure I got all the file
naming correct.
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Wednesday, August 15, 2012 2:25 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Archive: http://lists.debian.org/000601cd7c94$63afc4c0$2b0f4e40$@net
1. Load/boot ss4000e with the daily images kernel=v2.6.32-5
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/
It boots/runs 2.6.32-5
2. Cross-build new 3.4 kernel
3. Save modules and compress
$ export INSTALL_MOD_PATH=../modules-3.4 #make/put modules in
../modules-3.4
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- modules_install
$ cd ..
$ tar -zcvf modules-3.4.tar.gz modules-3.4 #compress
4. Fix zImage with Arnaud's devio trick to fix machine ID
$ ( devio 'wl 0xe3a01c04,4' 'wl 0xe38110bc,4'; cat zImage ) >
zImage-3.4.0-iop32x
5. Copy .config, System.map, zImage-3.4.0-iop32x, modules-3.4.tar.gz to tftp
server to upload them to ss4000e
6. Download these to a ss4000e working dir with tftp (needed to install
tftp)
7. Copy and rename downloaded to /boot per list below
8. Decompress modules-3.4.tar.gz. Copy the lib directory therein to /lib
9. Build initramfs in /boot
mkinitramfs -o initrd.img-3.4.0-iop32x 3.4.0
root@new-host:/boot# ls -l
total 10364
-rw-r--r-- 1 root root 81828 May 6 21:35 config-2.6.32-5-iop32x
-rw-r--r-- 1 root root 102426 Aug 17 10:08 config-3.4.0
lrwxrwxrwx 1 root root 26 Aug 16 17:34 initrd.img ->
initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2759115 Aug 16 17:59 initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2840619 Aug 17 10:09 initrd.img-3.4.0-iop32x
-rw-r--r-- 1 root root 945808 May 6 21:35 System.map-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1127522 Aug 17 09:32 System.map-3.4.0-iop32x
lrwxrwxrwx 1 root root 23 Aug 16 17:34 vmlinuz ->
vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1257376 May 6 21:34 vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1450536 Aug 17 09:33 zImage-3.4.0-iop32x
All the 3.4.0 files are in /boot but they are not yet linked. The ss4000e
will still boot as 2.6.32-5
10. Remake the 2 links so that initrd.img points to initrd-3.4.0-iop32x and
vmlinuz points to zImage-3.4.0-iop32x
11. Run flash-kernel to save
is initrd.img-3.4.0-iop32x too big?
12. Reboot and it should boot into 3.4 kernel??
I didn't actually take the last 3 steps. I'm not sure I got all the file
naming correct.
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstr...@scarlet.be]
Sent: Wednesday, August 15, 2012 2:25 PM
To: debia...@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
0 new messages