asiekierka wrote:RTL8168/8111, I am using the latest USB build as legacy USB BIOS support does NOT work for me in Kolibri despite working anywhere else. Also, perfectionism - it already is better than USB BIOS support.

But RTL8168/8111 should also work in the latest trunk night build, regardless of USB support - isn't it so? The USB support from CleverMouse right now makes around 25% of the computers stuck during boot-up, so it's not a good idea to place it in trunk. And I am 100% sure she will open-source the driver the moment it's ready.

You can still make the process of completing USB support faster if you post the test results from your computer.

yogev_ezra wrote:

asiekierka wrote:RTL8168/8111, I am using the latest USB build as legacy USB BIOS support does NOT work for me in Kolibri despite working anywhere else. Also, perfectionism - it already is better than USB BIOS support.

But RTL8168/8111 should also work in the latest trunk night build, regardless of USB support - isn't it so? The USB support from CleverMouse right now makes around 25% of the computers stuck during boot-up, so it's not a good idea to place it in trunk. And I am 100% sure she will open-source the driver the moment it's ready.

You can still make the process of completing USB support faster if you post the test results from your computer.

No, what I mean is, USB support only works in my computer with the CleverMouse USB build - otherwise I cannot use keyboard or mouse, even with BIOS legacy USB stuff enabled.

But I also need network stack support to have my RTL8168 network card work. The problem is, I need both and nobody has, well, both. That's why I need a build with both network and USB.

EDIT: tl;dr I need network for RTL8168 and USB for my keyboard/mouse as BIOS support does not work.

asiekierka wrote:No, what I mean is, USB support only works in my computer with the CleverMouse USB build - otherwise I cannot use keyboard or mouse, even with BIOS legacy USB stuff enabled.

Till here I understand.

asiekierka wrote:But I also need network stack support to have my RTL8168 network card work. The problem is, I need both and nobody has, well, both. That's why I need a build with both network and USB.

This I don't understand. Night builds from trunk should have RTL8168 support. If you use night build from trunk, what do you see on the board log when you try to use your network card?

Хабы, часть 2: реакция на события с портами. http://ftp.kolibrios.org/users/CleverMo ... kernel.mnt
Теперь при подключении/отключении устройств от хаба ядро должно выводить соответствующие сообщения на доску отладки. Кроме того, при инициализации хаба должны приходить сообщения о подключении всех устройств, которые там есть на момент инициализации.
Mario, на Roverbook лишний диск /bd теперь появляться не должен, ASRock должен нормально загружаться.

asiekierka wrote:CleverMouse, could you please build a USB-patched Kolibri kernel with the new network stack? I need both to run all my hardware successfully.

http://ftp.kolibrios.org/users/CleverMo ... el_net.mnt . I didn't test it at all, however, just merged USB changes into network branch.

EDIT: Also, any news on open-sourcing the code? Despite it being so incomplete, adding it to the official repo could help it by having more people add drivers/bugfixes, more people send in debug logs, etc. We are a small operating system and should cooperate, not compete, towards a single goal.

Nope, that wouldn't work. Writing drivers is not related to open-sourcing the code, drivers just need a known API, and API is documented. BTW two existing drivers are open-sourced, and nobody has written anything else despite that. Bugfixing, in theory, can be stimulated by opening the source, but in practice, nobody would care either - as a recent example, for quite long time there were two bugs in tmpdisk driver, which is uploaded in the repository with all related kernel code, but nobody has fixed it until I have decided to delay USB work and fix it myself. Note that tmpdisk is significantly shorter and simpler than the USB code.

asiekierka wrote:Also, perfectionism - it already is better than USB BIOS support.

There are system configurations where the current code is better than USB BIOS support. However, there are also configurations where BIOS support works, but the current code just breaks it.

CleverMouse wrote:на Roverbook лишний диск /bd теперь появляться не должен

Да, диск конечно исчез, но...

Spoiler:

U800.png (17.66 KiB)

Viewed 3902 times

BOARDLOG.TXT (2.32 KiB)

Downloaded 182 times

На KFM внимания обращать не надо - старенький он.

CleverMouse wrote:ASRock должен нормально загружаться.

Spoiler:

Boardlog_asrock.txt (18.08 KiB)

Downloaded 170 times

1. Втыкал/вытыкал мыши. Одна из мышей на 3-й раз зависает, но при дальнейших втыканиях продолжает работать.
2. Втыкал/вытыкал клавиатуру. Проблем нет.
3. Втыкал/вытыкал, в него втыкал мышь и видеокамеру, последовательно во все 4 разъема.
4. Втыкал/вытыкал веб-камеру.
5. Флешка как /bd/ не отображается.

Дополнительно: на Roverbook U800 теперь разделы жесткого диска после первого - не работают. KFM падает, а KFAR предлагает отказаться или попробовать еще раз.

Я обновила ядро, теперь /bd128 появляться не должен. Возможно, проблемы с жёстким диском на Roverbook были вызваны этой же проблемой, тогда они тоже уйдут.

ASUS M3N78-VM - Athlon II x2 245

Spoiler:

asus.jpg (451.94 KiB)

Viewed 3873 times

1. Хаб не распочухался, пишет ошибку с дескриптором.
2. Флешка не распочухалась, пишет ошибку с дескриптором.
Надеюсь это фото экрана хоть чем-то поможет.
Мышка и клавиатура работают без проблем.

Roverbook U800 - все работает, лог забыл сохранить. Хаб распочухался с устройствами.

В логе ASRock ничего подозрительного. Может быть, один раз с контактами было что-то не то, например, мышь не до конца вставлена?
Как будет вести себя http://ftp.kolibrios.org/users/CleverMo ... ernel2.mnt на ASUS M3N78-VM?

CleverMouse wrote:В логе ASRock ничего подозрительного. Может быть, один раз с контактами было что-то не то, например, мышь не до конца вставлена?

Нет, это сама мышка походу нестабильная. Другая мышка без проблем работает - коммутацию отрабатывает стабильно. А с нестабильной проявляется на всех компьютерах, но нерегулярно.

И в других операционных системах тоже?