PicUntu-4.5-nand-BasicGUI installer - One file, few click install.

[kotsos75]

ok i have flash this kernel and the graphics working good. now i mast do the step 9 again ?
becose i have done bofore the flushing and was working

now file rkwifi.ko.3.0.72+ its not found
and the pc restarts after while

[tyeo098]

The kernel and the filesystem are separate.

Think of it like starter and engine in a car.

Starter = kernel
Engine = filesystem

You can change the starter for a different one but it does not affect the petrol in the tank for the engine

Likewise, you can switch kernels all day long and still use the same filesystem, all your changes and files will still remain.

That might be bad analogy, but I hope you understand.

[kotsos75]

The kernel and the filesystem are separate.

Think of it like starter and engine in a car.

Starter = kernel
Engine = filesystem

You can change the starter for a different one but it does not affect the petrol in the tank for the engine

Likewise, you can switch kernels all day long and still use the same filesystem, all your changes and files will still remain.

That might be bad analogy, but I hope you understand.

so i try now to do the step 9 and i see file /lib/modules/rkwifi.ko.3.0.72+ not found
is this maybe moved when i have made the step 9 before i flash this kernel?

[tyeo098]

Yes, its probably moved to /lib/modules/3.0.72+/kernel/drivers/net like it says to do so in Step 9

Try running:

sudo modprobe rkwifi

[kotsos75]

sudo modprobe rkwifi

[/QUOTE]
if this command doing nothing then its ok i run this and nothing happens
i have try to run this sudo insmod /lib/modules/3.0.72+/kernel/drivers/net/rkwifi.ko
and says file exist

[tyeo098]

sudo modprobe rkwifi

if this command doing nothing then its ok i run this and nothing happens
i have try to run this sudo insmod /lib/modules/3.0.72+/kernel/drivers/net/rkwifi.ko
and says file exist[/QUOTE]

If modprobe does nothig it means it loaded and good.

You can do sudo lsmod and see rkwifi in list it means its running.
You do not need to worry about actual module location. Once you run depmod, kernel knows where it is.

Now launch WICD and connect to wifi!

[kotsos75]

if this command doing nothing then its ok i run this and nothing happens
i have try to run this sudo insmod /lib/modules/3.0.72+/kernel/drivers/net/rkwifi.ko
and says file exist

If modprobe does nothig it means it loaded and good.

You can do sudo lsmod and see rkwifi in list it means its running.
You do not need to worry about actual module location. Once you run depmod, kernel knows where it is.

Now launch WICD and connect to wifi![/QUOTE]

says no wireless networks found

[tyeo098]

If modprobe does nothig it means it loaded and good.

You can do sudo lsmod and see rkwifi in list it means its running.
You do not need to worry about actual module location. Once you run depmod, kernel knows where it is.

Now launch WICD and connect to wifi!

says no wireless networks found

Hmm... can you give me the output of

ls /etc/firmware

?

You may need to

sudo cp /system/etc/firmware/* /etc/firmware/

I think. Run

dmesg | grep firmware

and see where the kernel is trying to load the firmware from. Then go to that location and see if the firmware is there xD

[kotsos75]

Hmm... can you give me the output of

ls /etc/firmware

no such file or directory

You may need to

sudo cp /system/etc/firmware/* /etc/firmware/

/etc/firmware its not a directory

I think. Run

dmesg | grep firmware

to many lines but this say firmware_path=/etc/firmwar/

and see where the kernel is trying to load the firmware from. Then go to that location and see if the firmware is there xD

i can't find folder or file "firmware" there
shuld i try one more time from begining and do step 9 after flashing the kernel?

[tyeo098]

shuld i try one more time from begining and do step 9 after flashing the kernel?

No that wont change anything, like I said kernel and filesystem are separate.

Can you run the commands I posted in previous post?

Particularly give me output of

dmesg | grep -i firmware

[kotsos75]

Hmm... can you give me the output of

ls /etc/firmware

?

You may need to

sudo cp /system/etc/firmware/* /etc/firmware/

I think. Run

dmesg | grep firmware

and see where the kernel is trying to load the firmware from. Then go to that location and see if the firmware is there xD

No that wont change anything, like I said kernel and filesystem are separate.


Can you run the commands I posted in previous post?

Particularly give me output of

dmesg | grep -i firmware

[ 1868.232019] _dhdsdio_download_firmware: dongle image file download failed
[ 1868.463775] dhd_bus_select_firmware_name_by_chip: firmware_path=/etc/firmware/fw_RK901a2.bin

[tyeo098]

[ 1868.232019] _dhdsdio_download_firmware: dongle image file download failed
[ 1868.463775] dhd_bus_select_firmware_name_by_chip: firmware_path=/etc/firmware/fw_RK901a2.bin

Excellent.

Now, run

ls /etc/firmware

Do you see anything?
Particularly a file named fw_RK901a2.bin?

[kotsos75]

Excellent.

Now, run

ls /etc/firmware

Do you see anything?
Particularly a file named fw_RK901a2.bin?

ls: cannot access /etc/firmware no such file or directory

[kotsos75]

i just have try ls /system/etc/firmware and shows me many files inside

[kotsos75]

i just have try ls /system/etc/firmware and shows me many files inside
and yes this file fw_RK901a2.bin is inside
i have copy the full directory from /system/etc/firmware to etc firmware now
ls /etc/firmware shows me the files