Prev: success!
Next: solutions manual for Discrete Mathematics ( 6th Edition) by Richard Johnsonbaugh
From: taninux on 26 Mar 2010 13:08
Hi,

I installed Slackware 13 (64 bit) into an Asus UL30A.

As reported here:

http://www.xs4all.nl/~zwh/home-page/asus/asus-ul30a-linux.html

the driver ATL1C - for Atheros AR8132 Ethernet adapter - in kernel
2.6.29-6 seems to freeze the adapter.

Then I have to upgrade to the kernel 2.6.32-rc8 or a newer one.

Can I replace the kernel 2.6.29-6, in the slackware 13.0 system, with
the kernel 2.6.33 from current repository ?

If yes, how can I make this upgrade ?

Is it sufficent to install packages ./slackware64-current/slackware64/
a/kernel*.txz and update lilo, or I must compile a vanilla kernel from
source and install it by hand ?

Thanks

From: Chris Sorenson on 29 Mar 2010 01:16
taninux wrote:
> Hi,
>
> I installed Slackware 13 (64 bit) into an Asus UL30A.
>
> As reported here:
>
> http://www.xs4all.nl/~zwh/home-page/asus/asus-ul30a-linux.html
>
> the driver ATL1C - for Atheros AR8132 Ethernet adapter - in kernel
> 2.6.29-6 seems to freeze the adapter.
>
> Then I have to upgrade to the kernel 2.6.32-rc8 or a newer one.
>
> Can I replace the kernel 2.6.29-6, in the slackware 13.0 system, with
> the kernel 2.6.33 from current repository ?
>
> If yes, how can I make this upgrade ?
>
> Is it sufficent to install packages ./slackware64-current/slackware64/
> a/kernel*.txz and update lilo, or I must compile a vanilla kernel from
> source and install it by hand ?
>
> Thanks
>

You can install any kernel you want, just stick it in /boot and point
lilo.conf to it; run lilo and reboot. If the new kernel *doesn't* boot,
you have to have a procedure to recover. Fortunately, that's easy. Boot
from the Slackware install CD - make a mount point for your non-booting
root filesystem, for example

# mkdir /mnt/recover

Mount the non-booting root filesystem there, for example

# mount -t ext3 /dev/hda1 /mnt/recover

Change /dev/hda1 to whatever disk partition has your root filesystem.
Don't know? Try:

# fdisk /dev/hda

Command (m for help): p

....fdisk now prints a list of the partitions on /dev/hda...

Whatever partition is prefaced with an asterisk is your root partition.
Type 'q' to quit fdisk. Okay...

Edit /mnt/recover/etc/lilo.conf to point to your former kernel (or any
other previously known good kernel)

Now chroot the mounted filesystem:

# chroot /mnt/recover

Run lilo:

# lilo -v2

Now you should be able to boot back to the previously known good kernel.

DISCLAIMER: This is all off the top of my head. I've done this a bunch
of times but not recently so I could be remembering wrong or
forgetting steps. Getting old sucks... ;)
From: Giovanni on 29 Mar 2010 05:20
On 03/29/10 07:16, Chris Sorenson wrote:
> taninux wrote:
>> Hi,
>>
>> I installed Slackware 13 (64 bit) into an Asus UL30A.
>>
>> As reported here:
>>
>> http://www.xs4all.nl/~zwh/home-page/asus/asus-ul30a-linux.html
>>
>> the driver ATL1C - for Atheros AR8132 Ethernet adapter - in kernel
>> 2.6.29-6 seems to freeze the adapter.
>>
>> Then I have to upgrade to the kernel 2.6.32-rc8 or a newer one.
>>
>> Can I replace the kernel 2.6.29-6, in the slackware 13.0 system, with
>> the kernel 2.6.33 from current repository ?
>>
>> If yes, how can I make this upgrade ?
>>
>> Is it sufficent to install packages ./slackware64-current/slackware64/
>> a/kernel*.txz and update lilo, or I must compile a vanilla kernel from
>> source and install it by hand ?

> You can install any kernel you want, just stick it in /boot and point
> lilo.conf to it; run lilo and reboot. If the new kernel *doesn't* boot,
> you have to have a procedure to recover. Fortunately, that's easy. Boot
> from the Slackware install CD - make a mount point for your non-booting
> root filesystem, for example

No need to use the install CD if you configure lilo to boot also from
the old kernel.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >
From: Jerry Peters on 29 Mar 2010 16:22
Chris Sorenson <csoren(a)isd.net> wrote:
> taninux wrote:
>> Hi,
>>
>> I installed Slackware 13 (64 bit) into an Asus UL30A.
>>
>> As reported here:
>>
>> http://www.xs4all.nl/~zwh/home-page/asus/asus-ul30a-linux.html
>>
>> the driver ATL1C - for Atheros AR8132 Ethernet adapter - in kernel
>> 2.6.29-6 seems to freeze the adapter.
>>
>> Then I have to upgrade to the kernel 2.6.32-rc8 or a newer one.
>>
>> Can I replace the kernel 2.6.29-6, in the slackware 13.0 system, with
>> the kernel 2.6.33 from current repository ?
>>
>> If yes, how can I make this upgrade ?
>>
>> Is it sufficent to install packages ./slackware64-current/slackware64/
>> a/kernel*.txz and update lilo, or I must compile a vanilla kernel from
>> source and install it by hand ?
>>
>> Thanks
>>
>
> You can install any kernel you want, just stick it in /boot and point
> lilo.conf to it; run lilo and reboot. If the new kernel *doesn't* boot,
> you have to have a procedure to recover. Fortunately, that's easy. Boot
> from the Slackware install CD - make a mount point for your non-booting
> root filesystem, for example
>
> # mkdir /mnt/recover
>
> Mount the non-booting root filesystem there, for example
>
> # mount -t ext3 /dev/hda1 /mnt/recover
>
> Change /dev/hda1 to whatever disk partition has your root filesystem.
> Don't know? Try:
>
> # fdisk /dev/hda
>
> Command (m for help): p
>
> ...fdisk now prints a list of the partitions on /dev/hda...
>
> Whatever partition is prefaced with an asterisk is your root partition.
> Type 'q' to quit fdisk. Okay...
>
> Edit /mnt/recover/etc/lilo.conf to point to your former kernel (or any
> other previously known good kernel)
>
> Now chroot the mounted filesystem:
>
> # chroot /mnt/recover
>
> Run lilo:
>
> # lilo -v2
>
> Now you should be able to boot back to the previously known good kernel.
>
> DISCLAIMER: This is all off the top of my head. I've done this a bunch
> of times but not recently so I could be remembering wrong or
> forgetting steps. Getting old sucks... ;)

Why not avoid all of this by *adding* an entry for the new kernel to
lilo and selecting which one to boot? That's one of the features of a
boot manager, the ability to select a different kernel to boot.

Jerry
From: taninux on 30 Mar 2010 11:40
On 29 Mar, 07:16, Chris Sorenson <cso...(a)isd.net> wrote:
>
> You can install any kernel you want, just stick it in /boot and point
> lilo.conf to it; run lilo and reboot. If the new kernel *doesn't* boot,
> you have to have a procedure to recover.

Ok,

thank you :-)

 | 
Pages: 1
Prev: success!
Next: solutions manual for Discrete Mathematics ( 6th Edition) by Richard Johnsonbaugh