new kernel 3.2 does not boot on the dockstar

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Re: new kernel 3.2 does not boot on the dockstar

Postby ax0r7ag0z » Tue Jan 24, 2012 3:44 pm

Ok, i can type commands now but I cannot mount the second partition of my drive.
I get a "special device /dev/sda2 does not exist" error. Could you help me with
that "mount devpts" command you mentioned?

EDIT1
There must be a problem with udev...

EDIT2
I have no sdax block devices under dev!!
So I cannot mount the second partition of
my usb drive
ax0r7ag0z
 
Posts: 38
Joined: Mon Aug 30, 2010 8:59 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby cyberic » Tue Jan 24, 2012 6:12 pm

mknod /dev/sda1 b 8 1
mknod /dev/sda2 b 8 2
and so on....

I don't remember where mknod is, you may have to put the absolute path
Image
cyberic
 
Posts: 71
Joined: Sun Jan 15, 2012 11:26 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ax0r7ag0z » Tue Jan 24, 2012 7:06 pm

I will try mknod but I don't think it'll work...

Completely unrelated, but what happened to the plug apps wiki?
ax0r7ag0z
 
Posts: 38
Joined: Mon Aug 30, 2010 8:59 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ygator » Tue Jan 24, 2012 7:42 pm

Downgrading did not work for me. I still do not get my ttyUSB devices.
$this->bbcode_second_pass_code('', '[ 34.235313] udevd[69]: starting version 175
[ 34.677132] ch341: Unknown symbol usb_serial_disconnect (err 0)
[ 34.677154] ch341: Unknown symbol usb_serial_generic_open (err 0)
[ 34.677166] ch341: Unknown symbol usb_serial_generic_close (err 0)
[ 34.677178] ch341: Unknown symbol usb_serial_suspend (err 0)
[ 34.677202] ch341: Unknown symbol usb_serial_handle_dcd_change (err 0)
[ 34.677258] ch341: Unknown symbol usb_serial_probe (err 0)
[ 34.677269] ch341: Unknown symbol usb_serial_register (err 0)
[ 34.677281] ch341: Unknown symbol usb_serial_deregister (err 0)
[ 34.677293] ch341: Unknown symbol usb_serial_resume (err 0)
')
Here is what I have installed now.
$this->bbcode_second_pass_code('', '
module-init-tools 3.16-3
mkinitcpio 0.8.0-3
udev 175-1
linux 3.1.7-2
linux-api-headers 3.1.6-1
linux-firmware 20110822-1
linux-headers 3.1.7-2
util-linux 2.20.1-2
')
ygator
 
Posts: 97
Joined: Tue Aug 10, 2010 9:37 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ax0r7ag0z » Tue Jan 24, 2012 8:02 pm

now i get a

"mount: /dev/sda2 already mounted or "mountpoint" busy"

I must have screwed up my e2fsprogs real bad...
ax0r7ag0z
 
Posts: 38
Joined: Mon Aug 30, 2010 8:59 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ygator » Tue Jan 24, 2012 8:50 pm

Ok so I tried to manually loading the ch341 module and see that those messages are coming from modprobe.
So what did the upgrade do as I think I have downgraded everything the upgrade did?
$this->bbcode_second_pass_code('', ' modprobe ch341
FATAL: Error inserting ch341 (/lib/modules/3.1.7-2-ARCH/kernel/drivers/usb/serial/ch341.ko.gz): Unknown symbol in module, or unknown parameter (see dmesg)
')
And dmesg shoes those errors
$this->bbcode_second_pass_code('', '[ 984.501238] ch341: Unknown symbol usb_serial_disconnect (err 0)
[ 984.501262] ch341: Unknown symbol usb_serial_generic_open (err 0)
[ 984.501275] ch341: Unknown symbol usb_serial_generic_close (err 0)
[ 984.501288] ch341: Unknown symbol usb_serial_suspend (err 0)
[ 984.501313] ch341: Unknown symbol usb_serial_handle_dcd_change (err 0)
[ 984.501373] ch341: Unknown symbol usb_serial_probe (err 0)
[ 984.501385] ch341: Unknown symbol usb_serial_register (err 0)
[ 984.501398] ch341: Unknown symbol usb_serial_deregister (err 0)
[ 984.501410] ch341: Unknown symbol usb_serial_resume (err 0)
')
ygator
 
Posts: 97
Joined: Tue Aug 10, 2010 9:37 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby cyberic » Tue Jan 24, 2012 9:55 pm

@ygator: maybe you should backup your modules and kernel to a safe place, and do a mkinitcpio again?
Image
cyberic
 
Posts: 71
Joined: Sun Jan 15, 2012 11:26 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ygator » Tue Jan 24, 2012 10:14 pm

I got it working. I backup the root filesystem on one of the dockstars every midnight. So I was comparing the backup to what was running now. Even though I downgraded the packages that were installed today there were still a lot of files different. However, I focused on /lib/modules/3.1.7-2-ARCH and replaced each file one at a time doing a modprobe ch341. It finally worked when I put back modules.dep and modules.dep.bin. In looking through the module.dep file for ch341 I found that the one that did not work had the line:
kernel/drivers/usb/serial/ch341.ko.gz:
and the one from the midnight backup had:
kernel/drivers/usb/serial/ch341.ko.gz: kernel/drivers/usb/serial/usbserial.ko.gz
ygator
 
Posts: 97
Joined: Tue Aug 10, 2010 9:37 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby ygator » Tue Jan 24, 2012 10:20 pm

I am not sure why installing a new kernel would have changed modules on the older kernel.
I am also not sure why downgrading back to the older kernel would not have gotten me a module.dep[.bin] that worked.

There must be something else that is done that downgrading does not do to the modules.

@cyberic, thanks for the reply. Maybe the something else is the mkinitcpio you mentioned.
ygator
 
Posts: 97
Joined: Tue Aug 10, 2010 9:37 pm

Re: new kernel 3.2 does not boot on the dockstar

Postby WarheadsSE » Tue Jan 24, 2012 10:22 pm

From what we are seeing:

kmod sucks @ depmod.
kernel on certain v5 systems fails miserable on gzip compression.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 12 guests